| 1 |
On Wed, 3 Jan 2007 11:03:34 -0000, Nelson, David \(ED, PAR&D\) wrote: |
| 2 |
|
| 3 |
> Has the idea of distributing custom package.mask files occured? |
| 4 |
> This way you can "mask off" certain versions of software and hence limit |
| 5 |
> updates to minor changes. You can then use these on systems you want to |
| 6 |
> keep as stable as possible, use a test machine to test changes to the |
| 7 |
> package.mask and then roll it out. Might make management of many |
| 8 |
> workstations/servers easier. |
| 9 |
|
| 10 |
What happens when there are no unmasked version of a package available? |
| 11 |
You'd then have to start copying ebuilds to overlays etc. A "release |
| 12 |
tree" would be much easier, especially as it appears the devs may do the |
| 13 |
work for you from 2007.0. |
| 14 |
|
| 15 |
|
| 16 |
-- |
| 17 |
Neil Bothwick |
| 18 |
|
| 19 |
If at first you don't succeed, bugger. |
Archives