| 1 |
One problem I have with this is that it says all ebuilds should remain in the |
| 2 |
tree for a minimum of one year. 4 releases a year, and every package in the |
| 3 |
tree is going to have 4 versions that can't be cleaned out for at least a |
| 4 |
year. Not to mention that it's going to be hard to get developers in to the |
| 5 |
mindset of saving old ebuilds when we've been beating them ruthlessly about |
| 6 |
keeping portage clean for the past 6 months at least. Do you have any ideas |
| 7 |
about how to deal with this? |
| 8 |
|
| 9 |
On Monday 02 February 2004 09:17 am, Kurt Lieber wrote: |
| 10 |
> All -- |
| 11 |
> |
| 12 |
> I've posted GLEP 19 which talks about the inclusion of a new 'stable' tree |
| 13 |
> in portage that is updated on a periodic basis and only contains security |
| 14 |
> and major bugfixes out of cycle. |
| 15 |
> |
| 16 |
> http://www.gentoo.org/proj/en/glep/glep-0019.html |
| 17 |
> |
| 18 |
> Please take a moment to review the GLEP and offer any feedback or ask any |
| 19 |
> questions. |
| 20 |
> |
| 21 |
> --kurt |
| 22 |
|
| 23 |
-- |
| 24 |
Home -- http://www.brianandsara.net |
| 25 |
Gentoo -- http://gentoo.brianandsara.net |
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives