| 1 |
> 1. Automated generation of a portage overlay based on the currently installed |
| 2 |
> packages, these would then be safe from sync. The tool would need to be able |
| 3 |
> to drag ebuilds out of some sort of archive for existing machines. |
| 4 |
> 2. An easy way to introduce and manage and remove ebuilds in the overlay |
| 5 |
|
| 6 |
How is this different than making a tree based off of the snapshots |
| 7 |
created by releng for each release? Now, if you want to add newer stuff |
| 8 |
later on, it would be nice to have a tool to grab all the nessary |
| 9 |
ebuilds required for that newer ebuild. Perhaps thats what you're |
| 10 |
talking about. |
| 11 |
|
| 12 |
-- |
| 13 |
Lance Albertson <ramereth@g.o> |
| 14 |
Gentoo Infrastructure | Operations Manager |
| 15 |
|
| 16 |
--- |
| 17 |
GPG Public Key: <http://www.ramereth.net/lance.asc> |
| 18 |
Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 |
| 19 |
|
| 20 |
ramereth/irc.freenode.net |
Archives