Jeroen Roovers posted on Tue, 12 Jan 2010 03:22:05 +0100 as excerpted:
> net-nntp/inn-2.5.1 is in the tree and fixes many (QA) issues. [& etc]
Thanks! =:^)
(Not to be an aoler and metoo, but I asked some time ago and the
consensus seemed to be that thanks were good even if they meant an extra
On Mon, 11 Jan 2010 20:36:37 -0500, Richard Freeman
wrote:
> On 01/11/2010 06:30 PM, Arnaud Launay wrote:
>>
>> As a newsmaster, I'm a bit concerned by this.
>
> Yeah, inn seems like a really high-profile package to mask for removal.
> It would be conspicuous in its absence.
>
> Would it mak
On 01/11/10 09:47, Arfrever Frehtes Taifersar Arahesis wrote:
> 2010-01-11 04:55:02 Sebastian Pipping napisał(a):
> PYTHON_DEPEND="2:2.5:2.6"
> Dependency on Python 2.6 or 2.5.
>>
>> The colon (':') has two different semantics here.
>
> The colon is only separator of components, so i
On Tue, 12 Jan 2010 02:02:14 +0100
Jeroen Roovers wrote:
> I'm working on getting 2.5.1 in the tree (and fixing a USE=python and
> some other issues while I'm at it).
net-nntp/inn-2.5.1 is in the tree and fixes many (QA) issues. Please
track bug #300650 [1] if you want to stay informed of its
st
On 01/11/2010 06:30 PM, Arnaud Launay wrote:
As a newsmaster, I'm a bit concerned by this.
Yeah, inn seems like a really high-profile package to mask for removal.
It would be conspicuous in its absence.
Would it make sense to post on -dev BEFORE masking packages like this?
I'm sure there
Arnaud Launay posted on Tue, 12 Jan 2010 00:30:24 +0100 as excerpted:
> Hello,
>
> Le Mon, Jan 11, 2010 at 11:05:16PM +0200, Markos Chandras a écrit:
>> # Markos Chandras (11 Jan 2010) # Fails with
>> -Wl,--as-needed
>> # bug #182782. Removal in 30 days
>> net-nntp/inn
>
> As a newsmaster, I'm
On Tue, 12 Jan 2010 00:30:24 +0100
Arnaud Launay wrote:
> But, if I understand this announce correctly, the complete inn
> port will be dropped to oblivion.
Yes, and that shouldn't (and won't) happen.
> Wouldn't it be better to stabilize inn 2.5 (there's even a 2.5.1
> release out there, with a
On Mon, 11 Jan 2010 17:31:08 -0500
Mike Frysinger wrote:
> On Monday 11 January 2010 16:05:16 Markos Chandras wrote:
> > # Markos Chandras (11 Jan 2010)
> > # Fails with -Wl,--as-needed
> > # bug #182782. Removal in 30 days
> > net-nntp/inn
>
> is as-needed support really a valid reason for pun
Hello,
Le Mon, Jan 11, 2010 at 11:05:16PM +0200, Markos Chandras a écrit:
> # Markos Chandras (11 Jan 2010)
> # Fails with -Wl,--as-needed
> # bug #182782. Removal in 30 days
> net-nntp/inn
As a newsmaster, I'm a bit concerned by this.
By viewing bug #182782 , it seems to me that only inn <=2.4.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dne 11.1.2010 23:23, Brian Harring napsal(a):
> On Mon, Jan 11, 2010 at 09:25:51PM +0100, Raaal Porcel wrote:
>> scarabeus told me that the eclass can't be removed until two years since
>> the deprecation date, so...
>>
>> Removal of the eclass on 2012
Brian,
On Sun, Oct 25, 2009 at 6:50 PM, Brian Harring wrote:
> The proposal is pretty simple; if code modifies the vdb in any
> fashion, it needs to update the mtime on a file named
> '.modification_time' in the root of the vdb.
>
> For example-
>
> 1) ${PACKAGE_MANAGER} fires ups, builds a pkg.
On Monday 11 January 2010 16:05:16 Markos Chandras wrote:
> # Markos Chandras (11 Jan 2010)
> # Fails with -Wl,--as-needed
> # bug #182782. Removal in 30 days
> net-nntp/inn
is as-needed support really a valid reason for punting a package ? i dont
think it is.
-mike
signature.asc
Description:
On Mon, Jan 11, 2010 at 09:25:51PM +0100, Raaal Porcel wrote:
> scarabeus told me that the eclass can't be removed until two years since
> the deprecation date, so...
>
> Removal of the eclass on 2012/01/11
Reasoning? Prior to env saving we couldn't particularly punt
eclasses, but env saving is
# Markos Chandras (11 Jan 2010)
# Fails with -Wl,--as-needed
# bug #182782. Removal in 30 days
net-nntp/inn
--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
signature.asc
Description: This is a digitally signed message part.
As KDE 3 has been removed from the tree, the kde-* eclasses are no
longer used by anything remaining in the tree. These eclasses are
scheduled for removal on or about 2012/01/11.
signature.asc
Description: OpenPGP digital signature
scarabeus told me that the eclass can't be removed until two years since
the deprecation date, so...
Removal of the eclass on 2012/01/11
Raúl Porcel wrote:
> This is an ancient eclass that was used when the Compaq C Compiler still
> worked, but was removed from the tree some time ago.
>
> Remova
# Markos Chandras (11 Jan 2010)
# Qt3 application, doesn't have a maintainer and has a few open bugs.
# bug #299083. Removal in 30 days
app-dicts/qvortaro
Pick it up if you want to save it
--
Markos Chandras (hwoarang)
Gentoo Linux Developer [KDE/Qt/Sound/Sunrise/Kernel/AMD64/Bug-
wrangler/Treec
Hi,
I'd like to request feedback on the attached new ruby-ng-gnome2.eclass.
This eclass supersedes the current ruby-gnome2 eclass. It builds on
ruby-ng.eclass and is used to install the various components and
bindings of the ruby-gnome2 project.
This eclass fixes https://bugs.gentoo.org/show_bug.
This is an ancient eclass that was used when the Compaq C Compiler still
worked, but was removed from the tree some time ago.
Removal of the eclass on 2010/02/01.
It looks like what you really want is a ranged dependencies. From the
look of it though I have to second the "it does not seem intuitive"
opinion as it gives another meaning to the slot syntax marker (':').
Other than that, it seems like a worthy addition to the eclass.
--
Gilles Dartiguelongue
On Monday 11 of January 2010 01:25:45 Arfrever Frehtes Taifersar Arahesis
wrote:
> 2010-01-10 21:56:01 Fabian Groffen napisał(a):
> > On 10-01-2010 09:29:28 +0100, Arfrever Frehtes Taifersar Arahesis wrote:
> > > I would like to suggest introduction of support for PYTHON_DEPEND
> > > variable, whi
On 11-01-2010 08:29:32 +, Duncan wrote:
> Fabian Groffen posted on Mon, 11 Jan 2010 08:50:30 +0100 as excerpted:
>
> > On 11-01-2010 01:25:45 +0100, Arfrever Frehtes Taifersar Arahesis wrote:
> >> > Can you explain the intended use of this variable, and why normal
> >> > DEPEND is not sufficie
2010-01-11 08:50:30 Fabian Groffen napisał(a):
> On 11-01-2010 01:25:45 +0100, Arfrever Frehtes Taifersar Arahesis wrote:
> > > Can you explain the intended use of this variable, and why normal DEPEND
> > > is not sufficient?
> >
> > PYTHON_DEPEND is intented to simplify specification of dependenc
2010-01-11 04:55:02 Sebastian Pipping napisał(a):
> >>> PYTHON_DEPEND="2:2.5:2.6"
> >>> Dependency on Python 2.6 or 2.5.
>
> The colon (':') has two different semantics here.
The colon is only separator of components, so it has the same semantic.
Each component has strictly defined meaning.
Fabian Groffen posted on Mon, 11 Jan 2010 08:50:30 +0100 as excerpted:
> On 11-01-2010 01:25:45 +0100, Arfrever Frehtes Taifersar Arahesis wrote:
>> > Can you explain the intended use of this variable, and why normal
>> > DEPEND is not sufficient?
>>
>> PYTHON_DEPEND is intented to simplify speci
On 11-01-2010 01:25:45 +0100, Arfrever Frehtes Taifersar Arahesis wrote:
> > Can you explain the intended use of this variable, and why normal DEPEND
> > is not sufficient?
>
> PYTHON_DEPEND is intented to simplify specification of dependency on Python.
>
> PYTHON_DEPEND="2:2.5" is shorter than:
26 matches
Mail list logo
