View previous topic :: View next topic |
Author |
Message |
new_item n00b
Joined: 10 Jun 2011 Posts: 20 Location: Poland
|
Posted: Sun Feb 03, 2013 11:02 am Post subject: [SOLVED] Stable and unstable ebuilds in overlay |
|
|
Hi all!
I have some (100+) virtual machines, where I'm using ACCEPT_KEYWORDS="~amd64". I also have my own overlay, where form time to time people provide new ebuilds for some packages. This packages are more or less production ready.
Problem description:
I need to hide packages, which are not marked as stable. But I would like to leave ACCEPT_KEYWORDS="~amd64" in make.conf on machines.
Is there any 'second level' stable/unstable mechanizm in portage? I do not want use package.mask.
Probably problem is not to complicated, but I honestly can't find time to solve all tasks at once. Thank you for your time.
Last edited by new_item on Tue Feb 05, 2013 7:26 pm; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54099 Location: 56N 3W
|
Posted: Sun Feb 03, 2013 2:04 pm Post subject: |
|
|
new_item,
You can use package.keywords (or whatever its new name is) to force the use of stable packages on an otherwise testing system.
This means that your packages would need to be keyworded as stable. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
new_item n00b
Joined: 10 Jun 2011 Posts: 20 Location: Poland
|
Posted: Tue Feb 05, 2013 7:25 pm Post subject: |
|
|
I've decided to build testing packages like it was up to now. Name convention was: package-0.1.17. Now if developers decide that this package is production ready, then they will prepare package with exactly same content, but with number started from '1' (package-1.1.17).
This approach is convinient for me. Packages are builded only for internal use, so end user won't be confused.
On developer's servers there is always possibility to mask stable packages in package keywords.
NeddySeagoon , thank you for your time. |
|
Back to top |
|
|
|