leetNightshade
/
help-center-docs
Archived
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update all references to the Solus git URI 

As of today Solus has fully migrated away from the legacy cgit/gitolite
combination, to the fully configured Phabricator instance. As such, the
old URLs are no longer valid.

Signed-off-by: Ikey Doherty <ikey@solus-project.com>
This commit is contained in:
Ikey Doherty 2017-05-06 19:20:30 +01:00
parent bdd214bc1f
commit 73a7c00d03
No known key found for this signature in database
GPG Key ID: 78E2387015C1205F
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
packaging/building-a-package/en.md
View File

@ -42,7 +42,7 @@ To update solbuild, run: `sudo solbuild update`
Next you need to set up `common`, a set of make scripts that enables you to more easily manage, build, check, and publish packages.
You need to clone the common repository with git `sudo eopkg it git` by doing `git clone https://git.solus-project.com/common` in the same directory you will have sub-folders for packages you are building.
You need to clone the common repository with git `sudo eopkg it git` by doing `git clone https://dev.solus-project.com/source/common.git` in the same directory you will have sub-folders for packages you are building.
Next you need to set up symlinks. Do this from the same directory you executed the `git` command:
@ -77,7 +77,7 @@ make
You will be prompted to enter your password by sudo so dependencies may be downloaded and the necessary eopkg files may be generated.
You may find other `common` commands [here](https://git.solus-project.com/common/about/).
You may find other `common` commands [here](https://dev.solus-project.com/source/common/browse/master/about/).
Once you’ve achieved a successful build, the resulting `.eopkg` files will be moved to the current directory, along with the machine file, `pspec_*.xml` (currently `pspec_x86_64.xml`). We recommending checking the contents of your
generated eopkg file(s) to ensure everything is located in the appropriate locations. You can do this by using `lseopkg file_name.eopkg`.

2
packaging/updating-an-existing-package/en.md
View File

@ -5,7 +5,7 @@ title = "Updating an Existing Package"
This article will go over updating a package that is already in the Solus git repository.
The instructions below assume you have cloned the package's repository using the http link provided on the respective git page, [for example nano](https://git.solus-project.com/packages/nano). The process for submitting an updated package is the same as if it is a new package. Follow the steps [here](/articles/packaging/submitting-a-package/en).
The instructions below assume you have cloned the package's repository using the http link provided on the respective git page, [for example nano](https://dev.solus-project.com/source/nano/). The process for submitting an updated package is the same as if it is a new package. Follow the steps [here](/articles/packaging/submitting-a-package/en).
## Bumping a packaging

4
software/powerline-shell-prompt/en.md
View File

@ -7,8 +7,8 @@ title = "Powerline Shell Prompt"
## Installation
Powerline has two components, the plugin system itself ([powerline](https://git.solus-project.com/packages/powerline/)) and the
fonts ([powerline-fonts](https://git.solus-project.com/packages/powerline-fonts)). Both are available in the Software Center or via eopkg in a terminal:
Powerline has two components, the plugin system itself ([powerline](https://dev.solus-project.com/source/powerline/)) and the
fonts ([powerline-fonts](https://dev.solus-project.com/source/powerline-fonts/)). Both are available in the Software Center or via eopkg in a terminal:
``` bash
sudo eopkg it powerline powerline-fonts