[gentoo-dev] wine 20020228

[gentoo-dev] wine 20020228

[Per Wigren]

Just a note:
I did a:
# cp wine-20020122.ebuild wine-20020228.ebuild
and it works fine!

Regards
Per Wigren

Re: [gentoo-dev] wine 20020228

[jboyens]

Now if we could only make that automated. :)

Thanks for advising the list,
-- 
JR Boyens
jboyens@iastate.edu
---------------------------------------------
Speak softly and carry a +6 two-handed sword.
---------------------------------------------

Ebuild freeze (was: [gentoo-dev] wine 20020228)

[Arcady Genkin]

Per Wigren <wigren@home.se> writes:

> Just a note:
> I did a:
> # cp wine-20020122.ebuild wine-20020228.ebuild
> and it works fine!

Isn't it too bad that ebuild freeze is in effect?  ;^)

Having re-read the announcement, though, it's not clear to me whether
new versions of existing portages are subject to the freeze, or only
the newly submitted ebuilds...

Clarification, anyone?
-- 
Arcady Genkin
Don't read everything you believe.

Re: Ebuild freeze (was: [gentoo-dev] wine 20020228)

[Daniel Robbins]

On Mon, 2002-03-04 at 08:41, Arcady Genkin wrote:
> Per Wigren <wigren@home.se> writes:
> 
> > Just a note:
> > I did a:
> > # cp wine-20020122.ebuild wine-20020228.ebuild
> > and it works fine!
> 
> Isn't it too bad that ebuild freeze is in effect?  ;^)
> 
> Having re-read the announcement, though, it's not clear to me whether
> new versions of existing portages are subject to the freeze, or only
> the newly submitted ebuilds...
> 
> Clarification, anyone?

The main purpose of the ebuild freeze is to free up developer time.  If
you have some free time and want to update a few ebuilds, that's fine --
as long as you ensure the new versions work.

Best Regards,

-- 
Daniel Robbins                                  <drobbins@gentoo.org>
Chief Architect/President                       http://www.gentoo.org 
Gentoo Technologies, Inc.

Re: Ebuild freeze (was: [gentoo-dev] wine 20020228)

[Martin Schlemmer]

On Mon, 2002-03-04 at 18:10, Daniel Robbins wrote:
> On Mon, 2002-03-04 at 08:41, Arcady Genkin wrote:
> > Per Wigren <wigren@home.se> writes:
> > 
> > > Just a note:
> > > I did a:
> > > # cp wine-20020122.ebuild wine-20020228.ebuild
> > > and it works fine!
> > 
> > Isn't it too bad that ebuild freeze is in effect?  ;^)
> > 
> > Having re-read the announcement, though, it's not clear to me whether
> > new versions of existing portages are subject to the freeze, or only
> > the newly submitted ebuilds...
> > 
> > Clarification, anyone?
> 
> The main purpose of the ebuild freeze is to free up developer time.  If
> you have some free time and want to update a few ebuilds, that's fine --
> as long as you ensure the new versions work.
> 

And if you do decide to update it ... maybe move it to /usr ? :)

> Best Regards,
> 
> -- 
> Daniel Robbins                                  <drobbins@gentoo.org>
> Chief Architect/President                       http://www.gentoo.org 
> Gentoo Technologies, Inc.
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
-- 
Martin Schlemmer
Gentoo Linux Developer, Desktop Team
Cape Town, South Africa

Re: Ebuild freeze (was: [gentoo-dev] wine 20020228)

[Dan Armak]

On Monday 04 March 2002 18:18, Martin Schlemmer wrote:
> On Mon, 2002-03-04 at 18:10, Daniel Robbins wrote:
> > On Mon, 2002-03-04 at 08:41, Arcady Genkin wrote:
> > > Per Wigren <wigren@home.se> writes:
> > > > Just a note:
> > > > I did a:
> > > > # cp wine-20020122.ebuild wine-20020228.ebuild
> > > > and it works fine!
> > >
> > > Isn't it too bad that ebuild freeze is in effect?  ;^)
> > >
> > > Having re-read the announcement, though, it's not clear to me whether
> > > new versions of existing portages are subject to the freeze, or only
> > > the newly submitted ebuilds...
> > >
> > > Clarification, anyone?
> >
> > The main purpose of the ebuild freeze is to free up developer time.  If
> > you have some free time and want to update a few ebuilds, that's fine --
> > as long as you ensure the new versions work.
>
> And if you do decide to update it ... maybe move it to /usr ? :)
>
I already did that when I wrote the abovementioned 20020122 ebuild 
recently :-) It's masked, but I'll unmask it now since people have confirmed 
it works.

-- 
Dan Armak
Gentoo Linux Developer, Desktop Team (KDE)
Matan, Israel

Re: [gentoo-dev] wine 20020228

[Dan Armak]

On Monday 04 March 2002 16:21, Per Wigren wrote:
> Just a note:
> I did a:
> # cp wine-20020122.ebuild wine-20020228.ebuild
> and it works fine!
I'll test and commit the new ebuild. Thanks for letting us know. In the future 
though, the proper place for such notifications is on bugs.gentoo.org.

-- 
Dan Armak
Gentoo Linux Developer, Desktop Team (KDE)
Matan, Israel