ruby nacelle
Sometimes i want to create my own ebuild, but i don't want to update the ebuild as soon as new version is released.
So i came up with this...
This allows me to patch the ebuild and as soon as a new version is in the repository the patch is updated as well.
WARN: This has no security and has not been tested outside my very small usecase
Still wanted to share this with you...
indigo mountain
Gentoosh
ruby nacelle
Gentoosh
did another thing 😉
For context the one in the middle is update_provided.sh and the one on the right is /etc/portage/profile/package.provided
ruby nacelle
changed everything /etc/portage/profile/package.provided
fallow drum
@ruby nacelle this is very cool but I think it would be less complex to have a overlay B and autogenerate ebuilds for it after sync of overlay A
(B has priority over A)
This way you can more easily switch package versions if you need to install from overlay A
The copy strategy is loosely similar to what crossdev does
