Currently there are stages available for the following platforms:
These are stages targeting fairly new targets, or ones that do not have a lot of users.
Users should be cautious of using these targets for daily systems and expect issues using them for critical things.
Easiest solution: SystemRescueCD
It is possible to get all of our shiny stuff via anonymous git.
You can browse our repositories via cgit.
If you don’t already have Git set up:
git config --global user.name "<your real name>" git config --global user.email "<your email>"
cave to sync from this local clone.
/etc/paludis/repositories/<repo>.conf and change the line:
sync = git+https://git.exherbo.org/<repo>.git
sync = git+https://git.exherbo.org/<repo>.git local: git+file:///home/<user>/<path to local repo>
In case you like to work with branches you may want to add the following as well:
sync_options = local: --branch=<branch>
Then, you can sync from the local clone with
cave sync -s local <repo>. For more info on this see our workflow docs.
In case you like to use multiple branches at once or have your branches named differently depending on what topic they deal with and don’t want to modify the repository config file everytime you can use
cave sync -s local <repo> -r <commit-id>. Note that you don’t have to supply the full commit-id, you only need to provide at least the first 4 characters. Also keep in mind that when you amend a commit its commit-id changes, if you keep using the old commit-id you’ll sync the old version of that commit.
Make your changes in the local clone and commit the changes to the repository. Remember to actually commit the changes; otherwise,
cave will not see them since it is using
git pull to pull from the local clone. For more info on using Git see the Git book.
Test your changes:
cave sync -s local <repo> -r <commit-id> cave resolve -x1 <package modified>
If they are not to your liking, go back to step 5, using
git commit --amend and
git rebase -i as much as you want.
Submit your changes to Gitlab.