| 1 |
On Monday 04 March 2002 18:18, Martin Schlemmer wrote: |
| 2 |
> On Mon, 2002-03-04 at 18:10, Daniel Robbins wrote: |
| 3 |
> > On Mon, 2002-03-04 at 08:41, Arcady Genkin wrote: |
| 4 |
> > > Per Wigren <wigren@××××.se> writes: |
| 5 |
> > > > Just a note: |
| 6 |
> > > > I did a: |
| 7 |
> > > > # cp wine-20020122.ebuild wine-20020228.ebuild |
| 8 |
> > > > and it works fine! |
| 9 |
> > > |
| 10 |
> > > Isn't it too bad that ebuild freeze is in effect? ;^) |
| 11 |
> > > |
| 12 |
> > > Having re-read the announcement, though, it's not clear to me whether |
| 13 |
> > > new versions of existing portages are subject to the freeze, or only |
| 14 |
> > > the newly submitted ebuilds... |
| 15 |
> > > |
| 16 |
> > > Clarification, anyone? |
| 17 |
> > |
| 18 |
> > The main purpose of the ebuild freeze is to free up developer time. If |
| 19 |
> > you have some free time and want to update a few ebuilds, that's fine -- |
| 20 |
> > as long as you ensure the new versions work. |
| 21 |
> |
| 22 |
> And if you do decide to update it ... maybe move it to /usr ? :) |
| 23 |
> |
| 24 |
I already did that when I wrote the abovementioned 20020122 ebuild |
| 25 |
recently :-) It's masked, but I'll unmask it now since people have confirmed |
| 26 |
it works. |
| 27 |
|
| 28 |
-- |
| 29 |
Dan Armak |
| 30 |
Gentoo Linux Developer, Desktop Team (KDE) |
| 31 |
Matan, Israel |
Archives