On 18:12 Thu 08 Nov , Andrej Kacian (ticho) wrote:
1.1 net-mail/getmail/getmail-4.7.7.ebuild
file :
http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-mail/getmail/getmail-4.7.7.ebuild?rev=1.1view=markup
plain:
On 23:15 Thu 08 Nov , Timo Gurr (tgurr) wrote:
1.1 net-print/cups/cups-1.3.4-r1.ebuild
file :
http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-print/cups/cups-1.3.4-r1.ebuild?rev=1.1view=markup
plain:
On 08:54 Fri 09 Nov , Wolfram Schlich (wschlich) wrote:
1.1 sys-process/fcron/fcron-3.0.4.ebuild
file :
http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-process/fcron/fcron-3.0.4.ebuild?rev=1.1view=markup
plain:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ingmar Vanhassel schrieb:
2007/11/9, René 'Necoro' Neumann [EMAIL PROTECTED]:
Steve Long schrieb:
René 'Necoro' Neumann wrote:
cmake-utils_src_enable python = -DENABLE_python=...
Wanted would be that it returned -DENABLE_PYTHON=...
I'm not
On Fri, 9 Nov 2007 00:13:39 -0800
Donnie Berkholz [EMAIL PROTECTED] wrote:
PDEPEND=
ppds? ( || (
(
net-print/foomatic-filters-ppds
net-print/foomatic-db-ppds
)
net-print/foomatic-filters-ppds
Donnie Berkholz kirjoitti:
On 23:15 Thu 08 Nov , Timo Gurr (tgurr) wrote:
1.1 net-print/cups/cups-1.3.4-r1.ebuild
file :
http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-print/cups/cups-1.3.4-r1.ebuild?rev=1.1view=markup
plain:
Ciaran McCreesh a écrit :
On Fri, 9 Nov 2007 00:13:39 -0800
Donnie Berkholz [EMAIL PROTECTED] wrote:
PDEPEND=
ppds? ( || (
(
net-print/foomatic-filters-ppds
net-print/foomatic-db-ppds
)
Robin H. Johnson wrote:
On Thu, Nov 08, 2007 at 07:52:49PM +0100, Marijn Schouten (hkBst) wrote:
Isn't there supposed to be a search box too?
Does anybody actually read the FAQ?
- Short packages2 TODO list
- Search: match a given string against: a substring in packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wulf C. Krueger schrieb:
On Friday, 09. November 2007 10:10:42 René 'Necoro' Neumann wrote:
But as I think, that the uppercase version is the common behavior here,
it should not need this extra PYTHON. :) That's why the patch ;)
Actually, the
On Friday, 09. November 2007 10:10:42 René 'Necoro' Neumann wrote:
But as I think, that the uppercase version is the common behavior here,
it should not need this extra PYTHON. :) That's why the patch ;)
Actually, the mixed-case is what we have encountered in most cases.
Furthermore, as you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
On Fri, 13 Apr 2007 14:21:16 +0200
Marius Mauch [EMAIL PROTECTED] wrote:
On Wed, 11 Apr 2007 15:41:01 +0100
Ciaran McCreesh [EMAIL PROTECTED] wrote:
* Phase changes: src_fetch - src_unpack - src_prepare -
src_configure -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
� wrote:
Wulf C. Krueger schrieb:
On Friday, 09. November 2007 10:10:42 Rený 'Necoro' Neumann wrote:
But as I think, that the uppercase version is the common behavior here,
it should not need this extra PYTHON. :) That's why the patch ;)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marijn Schouten (hkBst) wrote:
ý wrote:
Wulf C. Krueger schrieb:
On Friday, 09. November 2007 10:10:42 Rený 'Necoro' Neumann wrote:
But as I think, that the uppercase version is the common behavior here,
it should not need this extra PYTHON. :)
On Fri, 09 Nov 2007 18:41:38 +0100
Marijn Schouten (hkBst) [EMAIL PROTECTED] wrote:
Use case one: package is completely unversioned upstream.
Have src_fetch add a version as appropriate to the downloaded/mirrored
version. This will work as change of upstream sources will be
detected by all the
Usually it's best that ebuild variables follow the order that is in
skel.ebuild. So know we should decide where to place EAPI. I suggest we
put it it after LICENSE as that's where the more technical stuff like
SLOT starts. Attached a patch for skel.ebuild.
Regards,
Petteri
Index: skel.ebuild
On Fri, 09 Nov 2007 23:55:51 +0200
Petteri Räty [EMAIL PROTECTED] wrote:
Usually it's best that ebuild variables follow the order that is in
skel.ebuild. So know we should decide where to place EAPI. I suggest
we put it it after LICENSE as that's where the more technical stuff
like SLOT
What specifically are the phase invariancy and exclusivity requirements
for ebuilds? Currently PMS doesn't have anything to say about this;
clearly it needs to, since existing ebuilds fairly obviously do have
invariancy and exclusivity requirements.
Note that we're only discussing package manager
Ciaran McCreesh kirjoitti:
On Fri, 09 Nov 2007 23:55:51 +0200
Petteri Räty [EMAIL PROTECTED] wrote:
Usually it's best that ebuild variables follow the order that is in
skel.ebuild. So know we should decide where to place EAPI. I suggest
we put it it after LICENSE as that's where the more
On Freitag, 9. November 2007, Petteri Räty wrote:
What if I want to use EAPI=1 features in an eclass? So if we for example
we have an ebuild using EAPI=2 and then it inherits and eclass that sets
EAPI=1 for slot deps.
You check which EAPI the ebuild sets, then either continue or die. Handling
On Sat, 10 Nov 2007 01:39:18 +0100
Carsten Lohrke [EMAIL PROTECTED] wrote:
Handling depends a bit upon, if EAPI should always be downwards
compatible.
It won't be. It's likely that future EAPIs will introduce new
strictness requirements and remove certain legacy variables and
utilities.
--
Am 07.11.2007 um 14:09 schrieb Ferris McCormick:
On Wed, 2007-11-07 at 09:13 +0100, Alexis Ballier wrote:
Hi,
Yes, we should introduce tex, latex and kpathsea USE flags.
Anyone?
+1 for latex kpathsea. How/when do we start ? :) I'd say start
moving
useflags on a per package basis,
21 matches
Mail list logo
