On Fri, Sep 14, 2012 at 7:43 PM, Rick "Zero_Chaos" Farina
wrote:
> So just so we are clear, everyone but me thinks that DESCRIPTION="Based
> on the ${ECLASS} eclass" is a completely useful and critically required
> piece of code?
>
I don't think anyone really cares, and it doesn't seem like anyon
On Fri, Sep 14, 2012 at 1:51 PM, Rick "Zero_Chaos" Farina wrote:
> I have a personal vendetta on this subject. Several eclasses set a
> completely worthless description (and even more set a mostly worthless
> DESCRIPTION) which ends up contaminating the DESCRIPTION for an ebuild
> when inherit is d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/14/2012 05:27 PM, Michał Górny wrote:
> On Fri, 14 Sep 2012 17:18:16 -0400
> "Rick \"Zero_Chaos\" Farina" wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 09/14/2012 04:56 PM, Ciaran McCreesh wrote:
>>> On Fri, 14 Sep 2012
> On Sat, 16 Jun 2012, Ulrich Mueller wrote:
> On Sat, 16 Jun 2012, Sebastian Pipping wrote:
>> The "GPL-2+" file workaround doesn't sound to bad.
>> Call be picky, but we could actually use a "GPL-3+" file, too.
>> With that we could distinguish "exactly GPL 3" and "GPL 3 or later"
>> pr
On Fri, Sep 14, 2012 at 12:12 PM, Rick "Zero_Chaos" Farina
wrote:
> I didn't mean to pick on bzr.eclass, I think it's always wrong to do
> this. And you picked out the exact reasoning I did "I'm not sure if it
> would be worth the effort to compute a more accurate argument for
> addwrite." I thin
On Fri, 14 Sep 2012 17:18:16 -0400
"Rick \"Zero_Chaos\" Farina" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 09/14/2012 04:56 PM, Ciaran McCreesh wrote:
> > On Fri, 14 Sep 2012 16:51:54 -0400
> > "Rick \"Zero_Chaos\" Farina" wrote:
> >> I have a personal vendetta on this subj
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/14/2012 04:56 PM, Ciaran McCreesh wrote:
> On Fri, 14 Sep 2012 16:51:54 -0400
> "Rick \"Zero_Chaos\" Farina" wrote:
>> I have a personal vendetta on this subject. Several eclasses set a
>> completely worthless description (and even more set a mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 14 Sep 2012 16:51:54 -0400
"Rick \"Zero_Chaos\" Farina" wrote:
> I have a personal vendetta on this subject. Several eclasses set a
> completely worthless description (and even more set a mostly worthless
> DESCRIPTION) which ends up contamina
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a personal vendetta on this subject. Several eclasses set a
completely worthless description (and even more set a mostly worthless
DESCRIPTION) which ends up contaminating the DESCRIPTION for an ebuild
when inherit is done after DESCRIPTION is s
Hi,
After more than 5 years maintaining it (sh*t I'm old), I've
progressively lost interest in it, to the point that I consider it is
better that someone else takes care of it. So far I have dropped
maintainership to the video herd but vlc usually needs more specific
attention, so I fear that it m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/14/2012 11:51 AM, Ulrich Mueller wrote:
>> On Fri, 14 Sep 2012, Rick "Zero Chaos" Farina wrote:
>
>>> addwrite /
>> Am I reading this wrong, or is "addwrite /" being more than just a
>> little lazy? I know this isn't part of you
> On Fri, 14 Sep 2012, Rick "Zero Chaos" Farina wrote:
>> addwrite /
> Am I reading this wrong, or is "addwrite /" being more than just a
> little lazy? I know this isn't part of your change set but it has
> always bothered me that it needs to unlocking writing on the whole
> fil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/14/2012 05:01 AM, Ulrich Mueller wrote:
> In bug 434746 it has been suggested that ${WORKDIR} should look like a
> bzr branch or checkout. Proposed changes for bzr.eclass are included
> below, comprising the following:
>
> - bzr_fetch can option
On Fri, Sep 14, 2012 at 7:15 AM, Alex Legler wrote:
> A general note: The request makes one wonder a bit how much you actually
> care about your package if a few emails disturb you. Arches, Security,
> and users reporting issues are trying to help you get the package into a
> good shape.
I suspec
On 13.09.2012 09:29, Pacho Ramos wrote:
> […]
> OK, then, looks like the policy could be that, once all arches are done,
> maintainers cleanup ebuilds and unCC themselves, that way, if they are
> still getting mails from bug report is because they forgot to remove
> vulnerable versions and, if not
Am 2012-09-13 22:11, schrieb Rich Freeman:
On Thu, Sep 13, 2012 at 3:57 PM, Pacho Ramos
wrote:
El jue, 13-09-2012 a las 15:48 +0200, Alex Legler escribió:
Sorta OT but a general thing: I think you should CC teams you want
to
talk to and not only use the gentoo-systemd-flamewars^W^W-dev
mailin
In bug 434746 it has been suggested that ${WORKDIR} should look like a
bzr branch or checkout. Proposed changes for bzr.eclass are included
below, comprising the following:
- bzr_fetch can optionally call bzr checkout --lightweight instead of
bzr export. The default behaviour won't change, the n
17 matches
Mail list logo
