Re: [gentoo-dev] perforce client proper license

2009-03-22 Thread Nirbheek Chauhan
On Sun, Mar 22, 2009 at 2:58 AM, Alec Warner anta...@gentoo.org wrote: I think you will encounter namespace collisions, thats why I CC'd zac as he maintains mirror-dist ;p Why the hell didn't we think of this before!? :o The mirror-dist script *cannot* rename the upstream files for storage,

Re: [gentoo-dev] Make the policykit USE flag global

2009-03-22 Thread Nirbheek Chauhan
On Wed, Mar 18, 2009 at 6:42 PM, Olivier Crête tes...@gentoo.org wrote: Feel the trend? gnome-base/gnome-panel will follow soon. Lets make this global. Unless we decide that PolicyKit is the future and make it compulsory). If no one complains, I will make the changes in a couple days. So,

Re: [gentoo-dev] RFC: Deprecating EAPI0

2009-03-22 Thread Robert R. Russell
On Saturday 21 March 2009 19:03:45 AllenJB wrote: Patrick Lauer wrote: Hi all, with the discussion about EAPI3 we have now 4 (or 7, depending on how you count them ;) ) EAPIs available or almost available. This is getting quite confusing. To make our lives easier I would suggest

Re: [gentoo-dev] RFC: Deprecating EAPI0

2009-03-22 Thread Matti Bickel
Peter Alfredsen loki_...@gentoo.org wrote: I think we should start deprecating EAPI=0 usage *now* with a repoman warning whenever a new ebuild is committed that does not use EAPI=1 or EAPI=2. This warning should encourage use of the newest EAPI, EAPI=2. A general question, that just popped

EAPI roadmap (was: Re: [gentoo-dev] RFC: Deprecating EAPI0)

2009-03-22 Thread Thilo Bangert
Peter Alfredsen loki_...@gentoo.org said: On Sun, 22 Mar 2009 09:41:58 +0100 Matti Bickel m...@gentoo.org wrote: A general question, that just popped into my head when i was reading this: if i touch a ebuild which has EAPI=0, should i bump it to EAPI=2? Only if you take the time to read

[gentoo-dev] Re: EAPI roadmap

2009-03-22 Thread Serkan Kaba
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thilo Bangert yazmış: i doesnt make sense to introduce EAPI=2 into ebuilds, if we dont expect to have en EAPI=2 capable package manager stable within a reasonable timeframe. 2.1.6 is stable and supports EAPI2 - -- Sincerely, Serkan KABA Gentoo

Re: [gentoo-dev] RFC: Deprecating EAPI0

2009-03-22 Thread Dawid Węgliński
On Saturday 21 of March 2009 21:53:16 Patrick Lauer wrote: On Saturday 21 March 2009 21:21:47 Ciaran McCreesh wrote: On Sat, 21 Mar 2009 18:37:12 +0100 Patrick Lauer patr...@gentoo.org wrote: To make our lives easier I would suggest deprecating EAPI0 and migrating existing ebuilds

Re: [gentoo-dev] perforce client proper license

2009-03-22 Thread Robert Buchholz
On Sunday 22 March 2009, Nirbheek Chauhan wrote: On Sun, Mar 22, 2009 at 2:58 AM, Alec Warner anta...@gentoo.org wrote: I think you will encounter namespace collisions, thats why I CC'd zac as he maintains mirror-dist ;p Why the hell didn't we think of this before!? :o The mirror-dist

Re: [gentoo-dev] perforce client proper license

2009-03-22 Thread Ciaran McCreesh
On Sun, 22 Mar 2009 11:44:48 +0530 Nirbheek Chauhan nirbh...@gentoo.org wrote: On Sun, Mar 22, 2009 at 2:58 AM, Alec Warner anta...@gentoo.org wrote: I think you will encounter namespace collisions, thats why I CC'd zac as he maintains mirror-dist ;p Why the hell didn't we think of this

[gentoo-dev] please stop using foo-${PV}-bar.patch in other ebuild versions than ${PV}

2009-03-22 Thread Alin Năstac
Please do not apply patches that have ${P} prefix in other ebuild versions than ${PV}. Is that hard to create a new patch with a proper name? Cheers, Alin signature.asc Description: OpenPGP digital signature

Re: [gentoo-dev] please stop using foo-${PV}-bar.patch in other ebuild versions than ${PV}

2009-03-22 Thread Ulrich Mueller
On Sun, 22 Mar 2009, mrness wrote: Please do not apply patches that have ${P} prefix in other ebuild versions than ${PV}. Is that hard to create a new patch with a proper name? And multiply number and total size of files in ${FILESDIR}? Ulrich

Re: [gentoo-dev] please stop using foo-${PV}-bar.patch in other ebuild versions than ${PV}

2009-03-22 Thread Mounir Lamouri
On Sun, Mar 22, 2009 at 1:18 PM, Ulrich Mueller u...@gentoo.org wrote: On Sun, 22 Mar 2009, mrness wrote: Please do not apply patches that have ${P} prefix in other ebuild versions than ${PV}. Is that hard to create a new patch with a proper name? And multiply number and total size of files

Re: [gentoo-dev] please stop using foo-${PV}-bar.patch in other ebuild versions than ${PV}

2009-03-22 Thread Maciej Mrozowski
On Sunday 22 of March 2009 18:18:15 Ulrich Mueller wrote: On Sun, 22 Mar 2009, mrness wrote: Please do not apply patches that have ${P} prefix in other ebuild versions than ${PV}. Is that hard to create a new patch with a proper name? And multiply number and total size of files in

Re: [gentoo-dev] perforce client proper license

2009-03-22 Thread Nirbheek Chauhan
On Sun, Mar 22, 2009 at 8:32 PM, Ciaran McCreesh ciaran.mccre...@googlemail.com wrote: I quote: In EAPIs supporting arrows, if an arrow is used, the filename used when saving to \t{DISTDIR} shall instead be the name on the right of the arrow. When consulting mirrors (except for those

Re: [gentoo-dev] please stop using foo-${PV}-bar.patch in other ebuild versions than ${PV}

2009-03-22 Thread Nirbheek Chauhan
On Sun, Mar 22, 2009 at 10:54 PM, Mounir Lamouri mounir.lamo...@gmail.com wrote: Or just rename it ${PN}-bar.patch instead of ${P}-bar.patch if it is a patch for more than one ebuild version. But older ebuild has to be changed to make it works. The ${PV} in the patch name is a quick

[gentoo-dev] Gentoo Council Reminder for March 26

2009-03-22 Thread Donnie Berkholz
Sorry about the delay on this -- I wrote it on a computer that somehow fails at sending email and forgot it was in drafts. This is your friendly reminder! Same bat time (typically the 2nd 4th Thursdays at 2000 UTC / 1600 EST), same bat channel (#gentoo-council @ irc.freenode.net) ! If you

Re: [gentoo-dev] Gentoo Council Reminder for March 26

2009-03-22 Thread Ciaran McCreesh
On Sun, 22 Mar 2009 21:18:52 +0100 Donnie Berkholz dberkh...@gentoo.org wrote: If you have something you'd wish for us to chat about, maybe even vote on, let us know! Simply reply to this e-mail for the whole Gentoo dev list to see. Continuing the whole EAPI 3 thing...

[gentoo-dev] Re: please stop using foo-${PV}-bar.patch in other ebuild versions than ${PV}

2009-03-22 Thread Ryan Hill
On Sun, 22 Mar 2009 13:24:26 -0400 Mounir Lamouri mounir.lamo...@gmail.com wrote: On Sun, Mar 22, 2009 at 1:18 PM, Ulrich Mueller u...@gentoo.org wrote: On Sun, 22 Mar 2009, mrness wrote: Please do not apply patches that have ${P} prefix in other ebuild versions than ${PV}. Is that

Re: [gentoo-dev] Re: please stop using foo-${PV}-bar.patch in other ebuild versions than ${PV}

2009-03-22 Thread Sebastian Pipping
Ryan Hill wrote: Please do not apply patches that have ${P} prefix in other ebuild versions than ${PV}. Is that hard to create a new patch with a proper name? Um, why? I'm not having six identical patches with different version numbers in FILESDIR. Good point. Sebastian

[gentoo-dev] headless herds

2009-03-22 Thread Ryan Hill
These herds have no members: afterstep: net-mail/asmail x11-plugins/asapm x11-plugins/asclock x11-plugins/ascpu x11-plugins/asmem x11-plugins/asmon x11-plugins/astime x11-wm/afterstep Upstream is willing to maintain, just needs a contact. https://bugs.gentoo.org/180765 -- secure-tunneling:

Re: [gentoo-dev] please stop using foo-${PV}-bar.patch in other ebuild versions than ${PV}

2009-03-22 Thread Rémi Cardona
Le 22/03/2009 19:22, Nirbheek Chauhan a écrit : The ${PV} in the patch name is a quick indication of the age of a patch, the gnome herd especially *encourages* this behavior. What I used to do back when I was still bumping packages in the Gnome Herd, I would version the patch, but I would use

[gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2009-03-22 23h59 UTC

2009-03-22 Thread Robin H. Johnson
The attached list notes all of the packages that were added or removed from the tree, for the week ending 2009-03-22 23h59 UTC. Removals: net-mail/ezmlm 2009-03-16 19:54:26 tove net-mail/ezmlm-idx-mysql2009-03-16 19:54:27 tove

Re: [gentoo-dev] Re: please stop using foo-${PV}-bar.patch in other ebuild versions than ${PV}

2009-03-22 Thread Alin Năstac
On 3/22/09 11:47 PM, Ryan Hill wrote: On Sun, 22 Mar 2009 17:50:26 +0100 Alin Năstac mrn...@gentoo.org wrote: Please do not apply patches that have ${P} prefix in other ebuild versions than ${PV}. Is that hard to create a new patch with a proper name? Um, why? I'm not having

Re: [gentoo-dev] perforce client proper license

2009-03-22 Thread Markos Chandras
On Saturday 21 March 2009 14:06:09 Markos Chandras wrote: Hello folks, Qt-creator[1] program can support perforce[2] software configuration manager. My concern is the perforce license. According to their site[3] there is a dual(?) license. There is the standard commercial license[4]

[gentoo-dev] Re: please stop using foo-${PV}-bar.patch in other ebuild versions than ${PV}

2009-03-22 Thread Ryan Hill
On Mon, 23 Mar 2009 01:19:26 +0100 Alin Năstac mrn...@gentoo.org wrote: Fine, then remove $PV from patch name and use it in any ebuild version you want. Or just decouple the patch version from the ebuild version (foo-bar-r1.patch sounds OK to me). No. It's done this way for a reason. --

Re: [gentoo-dev] Re: please stop using foo-${PV}-bar.patch in other ebuild versions than ${PV}

2009-03-22 Thread Jeremy Olexa
Alin Năstac wrote: snip Fine, then remove $PV from patch name and use it in any ebuild version you want. Or just decouple the patch version from the ebuild version (foo-bar-r1.patch sounds OK to me). What exactly is your problem that you are trying to solve here? Posting to the community to

Re: [gentoo-dev] perforce client proper license

2009-03-22 Thread Alec Warner
On Sun, Mar 22, 2009 at 8:02 AM, Ciaran McCreesh ciaran.mccre...@googlemail.com wrote: On Sun, 22 Mar 2009 11:44:48 +0530 Nirbheek Chauhan nirbh...@gentoo.org wrote: On Sun, Mar 22, 2009 at 2:58 AM, Alec Warner anta...@gentoo.org wrote: I think you will encounter namespace collisions, thats

Re: [gentoo-dev] please stop using foo-${PV}-bar.patch in other ebuild versions than ${PV}

2009-03-22 Thread Jorge Manuel B. S. Vicetto
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alin Năstac wrote: Please do not apply patches that have ${P} prefix in other ebuild versions than ${PV}. Is that hard to create a new patch with a proper name? I opted to reply to your mail after reading all the other replies. FWIW, I agree with

[gentoo-dev] updating baselayout PERMS_PROTECT

2009-03-22 Thread Caleb Cushing
so from what I can see there doesn't appear to be any 'official' way of adding new directories, updating perms and the like in baselayout. my thought is someone who does an emerge -aveD world's system should for the most part be reset to 'factory' defaults. of course this leads to the problem...

[gentoo-dev] Re: headless herds

2009-03-22 Thread Ryan Hill
On Sun, 22 Mar 2009 17:38:16 -0700 Robin H. Johnson robb...@gentoo.org wrote: On Sun, Mar 22, 2009 at 05:55:38PM -0600, Ryan Hill wrote: secure-tunneling: net-analyzer/mping net-misc/corkscrew net-misc/ghamachi net-misc/hamachi net-misc/openssh net-misc/openswan

Re: [gentoo-dev] headless herds

2009-03-22 Thread Jeroen Roovers
On Sun, 22 Mar 2009 17:55:38 -0600 Ryan Hill dirtye...@gentoo.org wrote: These herds have no members: ... live-cd: app-admin/pwgen app-arch/pbzip2 app-misc/livecd-tools dev-python/pyparted dev-util/catalyst media-gfx/splash-themes-livecd sys-apps/ddcxinfo-knoppix sys-apps/gli