| 1 |
On Monday 26 September 2005 00:46, Lance Albertson wrote: |
| 2 |
> > 1. Automated generation of a portage overlay based on the currently |
| 3 |
> > installed packages, these would then be safe from sync. The tool would |
| 4 |
> > need to be able to drag ebuilds out of some sort of archive for existing |
| 5 |
> > machines. 2. An easy way to introduce and manage and remove ebuilds in |
| 6 |
> > the overlay |
| 7 |
> |
| 8 |
> How is this different than making a tree based off of the snapshots |
| 9 |
> created by releng for each release? Now, if you want to add newer stuff |
| 10 |
> later on, it would be nice to have a tool to grab all the nessary |
| 11 |
> ebuilds required for that newer ebuild. Perhaps thats what you're |
| 12 |
> talking about. |
| 13 |
|
| 14 |
Hello, |
| 15 |
|
| 16 |
I believe the snapshot only contains the newest versions of ebuilds? |
| 17 |
|
| 18 |
Perhaps i should be clearer: |
| 19 |
|
| 20 |
When initially run on an existing server it would identify all currently |
| 21 |
installed applications and copy the applications associated ebuild (version |
| 22 |
specific) to the portage overlay. This would create a portage tree specific |
| 23 |
to that machine. I imagine this is pretty easily done with a shell script. |
| 24 |
|
| 25 |
It would then be nice to have either a tool or for emerge to be somewhat aware |
| 26 |
of the fact that there is a separate tree and be able to add and remove |
| 27 |
ebuilds and manage the new tree at will. So `emerge -u postfix` would place |
| 28 |
the new courier ebuild into the new tree as well as upgrading, etc,etc. |
| 29 |
|
| 30 |
It's nothing grand, just automation of what could be with effort done by hand. |
| 31 |
|
| 32 |
It would serve three purposes: |
| 33 |
|
| 34 |
1. Protects the ebuilds of applications the admin can't/doesn't want to |
| 35 |
upgrade from dissappearing. |
| 36 |
2. Gives the admin more control over what gets upgraded, i realise |
| 37 |
that /etc/portage/ does this but requires explicit action to protect a |
| 38 |
version, this is passive. |
| 39 |
3. As an fringe benefit is easily backed up and allows another machine to be |
| 40 |
easily brought up with exactly the same applications and versions. |
| 41 |
|
| 42 |
I feel that i'm not articulating my thoughts very well and i apologise, |
| 43 |
perhaps i'll develop something for myself and see if it works before i |
| 44 |
trouble you all anymore. |
| 45 |
|
| 46 |
Cheers |
| 47 |
Phil |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
-- |
| 53 |
gentoo-server@g.o mailing list |
Archives