Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Eray Aslan <eray.aslan@...>
Subject: Re: Re: .la files removal news item (GLEP 42)
Date: Fri, 1 Oct 2010 18:42:20 +0300
On Fri, Oct 01, 2010 at 05:04:15PM +0200, Diego Elio Pettenò wrote:
> Il giorno ven, 01/10/2010 alle 17.31 +0400, Peter Volkov ha scritto:
> > It's better to avoid suggesting this as such things tend to stay for a
> > very long time on user's systems and since this'll became redundant
> > once
> > portage 2.1.9 will go stable soon it'll la files will be "fixed" twice
> > for no reason. 
> 
> It won't hurt anyway, and it'll definitely avoid people having to re-run
> lafilefixer manually from time to time.

Stabilize 2.1.9 and get rid of the post_src_install() stuff alltogether in
the news item?  A distro should not ask its users to fiddle with package
management software lightly.

Besides, if it is such a good idea -and it is- it should be part of
portage.

Why not push for stabilization of 2.1.9 and then do the news item?  Am I
missing something?

-- 
Eray


Replies:
Re: .la files removal news item (GLEP 42)
-- Diego Elio Pettenò
References:
.la files removal news item (GLEP 42)
-- Tomáš Chvátal
Re: .la files removal news item (GLEP 42)
-- Peter Volkov
Re: .la files removal news item (GLEP 42)
-- Diego Elio Pettenò
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: .la files removal news item (GLEP 42)
Next by thread:
Re: .la files removal news item (GLEP 42)
Previous by date:
Re: .la files removal news item (GLEP 42)
Next by date:
Re: .la files removal news item (GLEP 42)


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.