[gentoo-dev] aging ebuilds with unstable keywords

[gentoo-dev] aging ebuilds with unstable keywords

[Daniel Ahlberg]

Hi,

This is an automatically created email message.
http://gentoo.tamperd.net/stable has just been updated with 14512 ebuilds.

The page shows results from a number of tests that are run against the ebuilds. The tests are:
* if a version has been masked for 30 days or more.
* if an arch was in KEYWORDS in an older ebuild, but not in the newer ones.
* if SRC_URI contains hosts specified in thirdpartymirrors.
* if ebuild uses patch instead of epatch.
* if ebuild sets S to ${WORKDIR}/${P}.
* if ebuild redefines P, PV, PN or PF.
* if ebuild doesn't inherit eutils when it uses functions from eutils.
* if ebuild doesn't inherit flag-o-matic when it uses functions from flag-o-matic.
* if ebuild has $HOMEPAGE in SRC_URI (cosmetic).
* if ebuild has $PN in SRC_URI (cosmetic).
* if ebuild forces -fPIC flag to CFLAGS.
* if ebuild has deprecated WANT_AUTO(CONF|MAKE)_?_?.
* if ebuild uses is-flag -fPIC, should be changed to has_fpic.
* if ebuild appends $RDEPEND or $DEPEND to $RDEPEND or $DEPEND to $DEPEND.
* if ebuild has arch keyword(s) in iuse.
* if ebuild overrides MAKEOPTS.
* if ebuild has automake, autoconf or libtool in RDEPEND.
* if ebuild exists in ChangeLog.
* if ebuild installs COPYING and/or INSTALL into doc.

The database is updated once a day and this email is sent once a week.
Questions and comments may be directed to aliz@gentoo.org.

Script has been running for 206 minutes.
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] aging ebuilds with unstable keywords

[Paul de Vrieze]

[-- Attachment #1: Type: text/plain, Size: 315 bytes --]

On Monday 10 April 2006 05:26, Daniel Ahlberg wrote:
> * if ebuild has $PN in SRC_URI (cosmetic).

Why is this one bad? It creates some flexibility, and has the name of the 
package in one place only.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

[-- Attachment #2: Type: application/pgp-signature, Size: 200 bytes --]

[gentoo-dev] Re: aging ebuilds with unstable keywords

[Michael Sterrett -Mr. Bones.-]

Because you can't cut-n-paste the url when editing the ebuild.

Michael Sterrett
   -Mr. Bones.-
mr_bones_@gentoo.org

On Mon, 10 Apr 2006, Paul de Vrieze wrote:

> On Monday 10 April 2006 05:26, Daniel Ahlberg wrote:
>> * if ebuild has $PN in SRC_URI (cosmetic).
>
> Why is this one bad? It creates some flexibility, and has the name of the
> package in one place only.
>
> Paul
>
>
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Re: aging ebuilds with unstable keywords

[Mike Frysinger]

On Monday 10 April 2006 04:19, Michael Sterrett -Mr. Bones.- wrote:
> On Mon, 10 Apr 2006, Paul de Vrieze wrote:
> > On Monday 10 April 2006 05:26, Daniel Ahlberg wrote:
> >> * if ebuild has $PN in SRC_URI (cosmetic).
> >
> > Why is this one bad? It creates some flexibility, and has the name of the
> > package in one place only.
>
> Because you can't cut-n-paste the url when editing the ebuild.

eh ?  a sourceforge SRC_URI that uses $PN can easily be cut & paste ...
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Re: aging ebuilds with unstable keywords

[Michael Cummings]

On Mon, 10 Apr 2006 08:44:49 -0400
Mike Frysinger <vapier@gentoo.org> wrote:

> On Monday 10 April 2006 04:19, Michael Sterrett -Mr. Bones.- wrote:
> > On Mon, 10 Apr 2006, Paul de Vrieze wrote:
> > > On Monday 10 April 2006 05:26, Daniel Ahlberg wrote:
> > >> * if ebuild has $PN in SRC_URI (cosmetic).
> > >
> > > Why is this one bad? It creates some flexibility, and has the name
of the
> > > package in one place only.
> >
> > Because you can't cut-n-paste the url when editing the ebuild.
> 
> eh ?  a sourceforge SRC_URI that uses $PN can easily be cut & paste
...
> -mike

yeah - isn't this argument lost the second you have a SRC with mirror?
(i'm a known violator of this cosmetic convenience, so i might just be
biased here)

~mcummings
-- 
gentoo-dev@gentoo.org mailing list

[gentoo-dev] aging ebuilds with unstable keywords

[Daniel Ahlberg]

Hi,

This is an automatically created email message.
http://gentoo.tamperd.net/stable has just been updated with 14406 ebuilds.

The page shows results from a number of tests that are run against the ebuilds. The tests are:
* if a version has been masked for 30 days or more.
* if an arch was in KEYWORDS in an older ebuild, but not in the newer ones.
* if SRC_URI contains hosts specified in thirdpartymirrors.
* if ebuild uses patch instead of epatch.
* if ebuild sets S to ${WORKDIR}/${P}.
* if ebuild redefines P, PV, PN or PF.
* if ebuild doesn't inherit eutils when it uses functions from eutils.
* if ebuild doesn't inherit flag-o-matic when it uses functions from flag-o-matic.
* if ebuild has $HOMEPAGE in SRC_URI (cosmetic).
* if ebuild has $PN in SRC_URI (cosmetic).
* if ebuild forces -fPIC flag to CFLAGS.
* if ebuild has deprecated WANT_AUTO(CONF|MAKE)_?_?.
* if ebuild uses is-flag -fPIC, should be changed to has_fpic.
* if ebuild appends $RDEPEND or $DEPEND to $RDEPEND or $DEPEND to $DEPEND.
* if ebuild has arch keyword(s) in iuse.
* if ebuild overrides MAKEOPTS.
* if ebuild has automake, autoconf or libtool in RDEPEND.
* if ebuild exists in ChangeLog.
* if ebuild installs COPYING and/or INSTALL into doc.

The database is updated once a day and this email is sent once a week.
Questions and comments may be directed to aliz@gentoo.org.

Script has been running for 372 minutes.
-- 
gentoo-dev@gentoo.org mailing list

[gentoo-dev] Re: aging ebuilds with unstable keywords

[R Hill]

Daniel Ahlberg wrote:

> * if ebuild installs COPYING and/or INSTALL into doc.

Is this actually important?  There are a hell of a lot of ebuilds that fail
under this rule.  I'd like to start filing patches for some of the packages in
this list so I'm interested in knowing what's worth fixing and what's being
pedantic.

--de.


-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Re: aging ebuilds with unstable keywords

[Petteri Räty]

[-- Attachment #1: Type: text/plain, Size: 486 bytes --]

R Hill wrote:
> Daniel Ahlberg wrote:
> 
> 
>>* if ebuild installs COPYING and/or INSTALL into doc.
> 
> 
> Is this actually important?  There are a hell of a lot of ebuilds that fail
> under this rule.  I'd like to start filing patches for some of the packages in
> this list so I'm interested in knowing what's worth fixing and what's being
> pedantic.
> 

Not a blocker but just useless. Filing patches for ebuilds doing this is
greatly appreciated by at least me.

Regards,
Petteri

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

Re: [gentoo-dev] Re: aging ebuilds with unstable keywords

[Andrej Kacian]

[-- Attachment #1: Type: text/plain, Size: 629 bytes --]

On Sun, 20 Nov 2005 20:39:43 -0600
R Hill <dirtyepic.sk@gmail.com> wrote:

> > * if ebuild installs COPYING and/or INSTALL into doc.
> 
> Is this actually important?  There are a hell of a lot of ebuilds that fail
> under this rule.  I'd like to start filing patches for some of the packages
> in this list so I'm interested in knowing what's worth fixing and what's
> being pedantic.

Note that some of the packages caught by this test also install non-generic
(thus actually useful) INSTALL document.

-- 
Andrej "Ticho" Kacian <ticho at gentoo dot org>
Gentoo Linux Developer - net-mail, antivirus, sound, x86

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-dev] Re: aging ebuilds with unstable keywords

[R Hill]

Andrej Kacian wrote:
> On Sun, 20 Nov 2005 20:39:43 -0600
> R Hill <dirtyepic.sk@gmail.com> wrote:
> 
>>> * if ebuild installs COPYING and/or INSTALL into doc.
>> Is this actually important?  There are a hell of a lot of ebuilds that fail
>> under this rule.  I'd like to start filing patches for some of the packages
>> in this list so I'm interested in knowing what's worth fixing and what's
>> being pedantic.
> 
> Note that some of the packages caught by this test also install non-generic
> (thus actually useful) INSTALL document.

Yep, i did notice that.  Most of them on this list are, but i'm still weeding
through them.

--de.

-- 
gentoo-dev@gentoo.org mailing list

[gentoo-dev] aging ebuilds with unstable keywords

[Daniel Ahlberg]

Hi,

This is an automatically created email message.
http://gentoo.tamperd.net/stable has just been updated with 12219 ebuilds.

The page shows results from a number of tests that are run against the ebuilds. The tests are:
* if a version has been masked for 30 days or more.
* if an arch was in KEYWORDS in an older ebuild, but not in the newer ones.
* if SRC_URI contains hosts specified in thirdpartymirrors.
* if ebuild uses patch instead of epatch.
* if ebuild sets S to ${WORKDIR}/${P}.
* if ebuild redefines P, PV, PN or PF.
* if ebuild doesn't inherit eutils when it uses functions from eutils.
* if ebuild doesn't inherit flag-o-matic when it uses functions from flag-o-matic.
* if ebuild has $HOMEPAGE in SRC_URI (cosmetic).
* if ebuild has $PN in SRC_URI (cosmetic).
* if ebuild forces -fPIC flag to CFLAGS.
* if ebuild has deprecated WANT_AUTO(CONF|MAKE)_?_?.
* if ebuild uses is-flag -fPIC, should be changed to has_fpic.
* if ebuild appends $RDEPEND or $DEPEND to $RDEPEND or $DEPEND to $DEPEND.
* if ebuild has arch keyword(s) in iuse.
* if ebuild overrides MAKEOPTS.
* if ebuild has automake, autoconf or libtool in RDEPEND.
* if ebuild exists in ChangeLog.

The database is updated once a day and this email is sent once a week.
Questions and comments may be directed to aliz@gentoo.org.

Script has been running for 222 minutes.
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] aging ebuilds with unstable keywords

[Anthony Gorecki]

[-- Attachment #1: Type: text/plain, Size: 325 bytes --]

On Sunday, September 11, 2005 20:42, Daniel Ahlberg wrote:
> The page shows results from a number of tests that are run against the 
ebuilds.

Why does this script no longer include the results in the actual message? It 
was helpful to have both as a reference source.


-- 
Anthony Gorecki
Ectro-Linux Foundation

[-- Attachment #2: Type: application/pgp-signature, Size: 828 bytes --]

[gentoo-dev] Re: aging ebuilds with unstable keywords

[Duncan]

Anthony Gorecki posted <200509120109.37756.agorecki@ectrolinux.com>,
excerpted below,  on Mon, 12 Sep 2005 01:09:34 -0700:

> On Sunday, September 11, 2005 20:42, Daniel Ahlberg wrote:
>> The page shows results from a number of tests that are run against the
> ebuilds.
> 
> Why does this script no longer include the results in the actual message?
> It was helpful to have both as a reference source.

Well, the idea was helpful, but (as an amd64 user) I'm not entirely sure
the implementation was all that helpful.

The problem was due to the non-x86 "imlate" tracking.  Unfortunately, it
didn't work right, with the result normally meaning the top-10 spots as
listed in the message, were all ~amd64 entries where ~arch (for
some arch, normally x86) had been added several hundred days
earlier (before there /was/ a Gentoo amd64 arch, AFAIK), because it had no
way of tracking when the ~amd64 keyword was added, and incorrectly assumed
that the package had been ~amd64 since the package was keyworded ~arch for
/one/ arch at that point.

As one of the newer and more active archs, just then adding ~arch for
the first time to many apps, this was particularly frustrating for amd64,
since it left the impression the amd64 arch-team were a bunch of slackers
(no offense to slackware folks) that left packages in ~arch for hundreds
of days at a time, for little reason.

So...  if the script now ignores that factor, at least when calculating
the top-10, or if it has been fixed to correct the issue (a non-trivial
task, someone remarked at one point, because the info wasn't directly
available), and assuming there are no other such "spammer factors", it
/could/ be /very/ useful.  However, personally, at least, I'd /not/ like
to see it return in the broken state it was in, as I can't imagine that
being anything but frustration, to those responsible for the ebuilds
wrongly listed, due to a broken script.  (Not that my personal opinion
means a lot as "just" a user, on a dev list, but FWIW, whatever /that/ may
be.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@gentoo.org mailing list

[gentoo-dev] aging ebuilds with unstable keywords

[Daniel Ahlberg]

Hi,

This is an automatically created email message.
http://gentoo.tamperd.net/stable has just been updated with 8357 ebuilds.

The page shows results from a number of tests that are run against the ebuilds. The tests are:
* if a version has been masked for 30 days or more.
* if an arch was in KEYWORDS in an older ebuild, but not in the newer ones.
* if SRC_URI contains hosts specified in thirdpartymirrors.
* if ebuild uses patch instead of epatch.
* if ebuild sets S to ${WORKDIR}/${P}.
* if ebuild redefines P, PV, PN or PF.
* If the use flags in the ebuild matches those in IUSE.
* If ebuild sets IUSE.
* if ebuild doesn't inherit eutils when it uses functions from eutils.
* if ebuild doesn't inherit flag-o-matic when it uses functions from flag-o-matic.
* if ebuild has $HOMEPAGE in SRC_URI (cosmetic).
* if ebuild has $PN in SRC_URI (cosmetic).
* if ebuild forces -fPIC flag to CFLAGS.
* if ebuild has deprecated WANT_AUTO(CONF|MAKE)_?_?.
* if ebuild uses is-flag -fPIC, should be changed to has_fpic.
* if ebuild appends $RDEPEND or $DEPEND to $RDEPEND or $DEPEND to $DEPEND.
* if ebuild has arch keyword(s) in iuse.
* if ebuild overrides MAKEOPTS.


TOP TEN:
========

dev-tex/eurosym-1.2 - 905 days (~ppc)
media-video/mpeg2vidcodec-12-r1 - 892 days (~mips)
x11-plugins/wmix-3.0-r1 - 892 days (~ppc ~sparc)
app-office/gnofin-0.8.4 - 892 days (~amd64)
x11-plugins/asclock-2.0.12 - 892 days (~mips)
app-office/sc-7.12 - 892 days (~amd64)
x11-misc/e16keyedit-0.2 - 892 days (~amd64)
net-misc/smssend-3.2 - 892 days (~sparc)
x11-misc/xkeycaps-2.46 - 892 days (~amd64)
dev-python/orbit-python-0.3.1 - 892 days (~ppc)

Questions and comments may be directed to aliz@gentoo.org.

Script has been running for 48 minutes.

--
gentoo-dev@gentoo.org mailing list

[gentoo-dev] Re: aging ebuilds with unstable keywords

[Jörg Schaible]

Daniel Ahlberg wrote:

> * if ebuild doesn't inherit flag-o-matic when it uses functions from

Some time ago I read here on the list, that you can/should flag-o-matic now,
since it is included automatically ?!??

-- Jörg


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Re: aging ebuilds with unstable keywords

[Aron Griffis]

[-- Attachment #1: Type: text/plain, Size: 421 bytes --]

Jörg Schaible wrote:	[Mon Jul 12 2004, 02:00:55PM EDT]
> Some time ago I read here on the list, that you can/should flag-o-matic now,
> since it is included automatically ?!??

We've talked about inheriting both flag-o-matic and eutils
automatically, but it's not the current implementation.  At the moment
they both need to be inherited explicitly.

Regards,
Aron

--
Aron Griffis
Gentoo Linux Developer


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]