Jonathan Smith wrote:
you could simply make the default:
src_configure() {
[ -f ./configure ] econf || die
}
No need, this will do fine as a default:
src_configure() {
econf || die
}
Since econf already checks for a configure script and does nothing if it can't
find one...
On 07/07/05, Daniel Drake [EMAIL PROTECTED] wrote:
src_configure() {
econf || die
}
Since econf already checks for a configure script and does nothing if it can't
find one...
Yours might do. The one I have in /usr/sbin/ebuild.sh from portage
2.0.51.22-r1 says this:
econf() {
On Wed, 2005-07-06 at 15:46 -0700, Greg KH wrote:
So, anyone have any objections to me changing the default udev naming
scheme in this manner?
I'm all for the move - I always disable the devfs naming scheme in udev
anyways.
Next up, that loony block device naming scheme (more on that
On Wed, 2005-07-06 at 02:00 +0200, Sven Wegener wrote:
I want developers to take a look at the list and see if packages the
maintain are listed. I'm aware that the list is quite large and still
contains a lot of false positives. I can whitelist packages for DEPEND
or RDEPEND either general,
Sven Wegener posted [EMAIL PROTECTED],
excerpted below, on Thu, 07 Jul 2005 02:04:04 +0200:
We would like to split up src_compile. The new src_configure should just
do the econf part and src_compile should do the emake part. This
represents the general 3-step[1] installation in a much better
On Thursday 07 July 2005 14:19, Ned Ludd wrote:
I would be in favor of EAPI= or an even shorter variable name.
EAPI is probably the best name, EV makes it possible to confuse it with
PV-like variables, referring to the versions of the package, not portage
itself.
--
Diego Flameeyes Pettenò
On Thu, 2005-07-07 at 02:04 +0200, Sven Wegener wrote:
Hi all!
I'm writing this mail to bring you a thought we had over on freenode in
the #gentoo-portage channel. We would like to split up src_compile. The
new src_configure should just do the econf part and src_compile should
do the emake
On Wed, 2005-07-06 at 15:46 -0700, Greg KH wrote:
To start with, the 061 version of udev offers a big memory savings if
you use the default kernel name of a device[3]. If you do that, it does
not create a file in its database in /dev/.udevdb/
So if we were to switch to udev 061 in genkernel,
On 07/07/05, Sven Wegener [EMAIL PROTECTED] wrote:
I'm writing this mail to bring you a thought we had over on freenode in
the #gentoo-portage channel. We would like to split up src_compile. The
new src_configure should just do the econf part and src_compile should
do the emake part. This
On 07/07/05, Ned Ludd [EMAIL PROTECTED] wrote:
I would be in favor of EAPI= or an even shorter variable name.
strlen(EBUILD_FORMAT) * 19546 = 249K
strlen(EAPI) * 19546 = 77K
strlen(EV) * 19546 = 39K
Where 19546 is the number if ebuilds in the tree as.
If you're that interested in saving
On Thu, 2005-07-07 at 15:25 +0100, twofourtysix wrote:
Whilst you're at it... Why not split unpack up into, say, unpack and
prepare? Make src_unpack's default stay the same and use src_prepare
for patches and autotools things? This will avoid the pointless
duplication of the default src_unpack
ebuild(5) provides an example of the DEPEND string for a package which
can handle exactly one of several different video interfaces:
|| (
sdl? ( media-libs/libsdl )
svga? ( media-libs/svgalib )
opengl? ( virtual/opengl )
ggi? ( media-libs/libggi )
On Thursday 07 July 2005 11:05 am, twofourtysix wrote:
ebuild(5) provides an example of the DEPEND string for a package which
can handle exactly one of several different video interfaces:
snip
I've been using a similar construct in one of my local ebuilds. My
build code is along the lines of:
On Thu, 7 Jul 2005 16:05:24 +0100 twofourtysix [EMAIL PROTECTED]
wrote:
| However, a recently overheard conversation on IRC suggests that this
| is incorrect. Would someone with slightly less intolerance for
| clueless newbies be kind enough to explain why exactly this is wrong,
| and how to
On Thu, 7 Jul 2005 11:17:48 -0400
Mike Frysinger [EMAIL PROTECTED] wrote:
the only argument ive heard against using || ( ) is binary
packages due to the 'accept any' nature of || ( )
There are issues that don't affect only binary package but also
from-sources installation. The example was:
||
On Thu, 7 Jul 2005 17:14:36 +0100
Ciaran McCreesh [EMAIL PROTECTED] wrote:
On Thu, 7 Jul 2005 18:04:59 +0200 Thomas de Grenier de Latour
[EMAIL PROTECTED] wrote:
| Thus, the src_compile should use some has_version instead:
| if has_version media-lib/sdl ; then
| emake game.sdl ||
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
every single install has an issue with python-fchksum and gcc this
needs to be merged after python otherwise python calls the wrong
compiler. Hope we can get this fixed before our 2005.1 release.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1
twofourtysix wrote:
On 07/07/05, Ned Ludd [EMAIL PROTECTED] wrote:
I would be in favor of EAPI= or an even shorter variable name.
strlen(EBUILD_FORMAT) * 19546 = 249K
strlen(EAPI) * 19546 = 77K
strlen(EV) * 19546 = 39K
Where 19546 is the number if ebuilds in the tree as.
After seeing the strange and unusual postings that we get sometimes in
bugzilla.. We've had it!
please consult here:
http://www.gentoo.org/doc/en/bugzilla-howto.xml
Going to this page now ensures that hitman are not sent to your home right
away. However, if you read this doc and still
maillog: 06/07/2005-15:46:51(-0700): Greg KH types
Ok, now that devfs is removed from the 2.6 kernel tree[1], I think it's
time to start to revisit some of the /dev naming rules that we currently
are living with[2].
To start with, the 061 version of udev offers a big memory savings if
you
On Thu, 2005-07-07 at 12:15 -0500, Jory A. Pratt wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
every single install has an issue with python-fchksum and gcc this
needs to be merged after python otherwise python calls the wrong
compiler. Hope we can get this fixed before our 2005.1
On Thu, 2005-07-07 at 08:19 -0400, Ned Ludd wrote:
I would be in favor of EAPI= or an even shorter variable name.
strlen(EBUILD_FORMAT) * 19546 = 249K
strlen(EAPI) * 19546 = 77K
strlen(EV) * 19546 = 39K
Where 19546 is the number if ebuilds in the tree as.
So, the size of the tree is
On Thursday 07 July 2005 01:42 pm, Chris Gianelloni wrote:
On Thu, 2005-07-07 at 12:15 -0500, Jory A. Pratt wrote:
every single install has an issue with python-fchksum and gcc this
needs to be merged after python otherwise python calls the wrong
compiler. Hope we can get this fixed before
Hi,
Chris White wrote:
jforman
EBUILD BUGS GO IN GENTOO LINUX PRODUCT
STOP MARKING EVERY BUG AS A BLOCKER
/jforman
What about changing the description for the severity field rather than
jelling at users? Honestly, if a bug prevents you from using your
favourite app, wouldn't you select
On Tuesday 05 July 2005 02:39, Martin Schlemmer wrote:
Also as already asked, what about the chicken egg issue ... (think tar
needing tar, or gzip needing gzip to unpack)?
The stages could come primed with the data that the packages on them are
already installed.
pgpyh0WySyPe7.pgp
7.7.2005, 19:42:56, Chris Gianelloni wrote:
On Thu, 2005-07-07 at 12:15 -0500, Jory A. Pratt wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
every single install has an issue with python-fchksum and gcc this
needs to be merged after python otherwise python calls the wrong
compiler.
On Jul 7, 2005, at 6:56 AM, John Myers wrote:
On Tuesday 05 July 2005 02:39, Martin Schlemmer wrote:
Also as already asked, what about the chicken egg issue ... (think
tar
needing tar, or gzip needing gzip to unpack)?
The stages could come primed with the data that the packages on
Martin Schlemmer posted [EMAIL PROTECTED], excerpted
below, on Thu, 07 Jul 2005 15:55:45 +0200:
Lastly on an unrelated note ... I have a rule:
-
# cat /etc/udev/rules.d/40-dm.rules
KERNEL=dm-[0-9]*, PROGRAM=/sbin/devmap_name %M %m, NAME=mapper/%c,
SYMLINK=%c
-
And in theory
Aron Griffis posted [EMAIL PROTECTED], excerpted
below, on Thu, 07 Jul 2005 10:19:54 -0400:
(2) new portage uses rsync exclusions to ignore the digests since
it only needs the new-style manifest:
rsync --exclude '**/files/digest*' --delete-excluded
This wouldn't
On Thu, 2005-07-07 at 12:44 -0700, Duncan wrote:
Martin Schlemmer posted [EMAIL PROTECTED], excerpted
below, on Thu, 07 Jul 2005 15:55:45 +0200:
Lastly on an unrelated note ... I have a rule:
-
# cat /etc/udev/rules.d/40-dm.rules
KERNEL=dm-[0-9]*, PROGRAM=/sbin/devmap_name %M
Current (possibly unwritten) policy:
- eclasses declare USE-flags they honor in their own IUSE
- ebuilds declare USE-flags they honor in their own IUSE
- ebuilds do not declare USE-flags honored by eclasses they inherit
This policy has been around for a while. It assumes that all the
On Thu, Jul 07, 2005 at 03:55:45PM +0200, Martin Schlemmer wrote:
On Wed, 2005-07-06 at 15:46 -0700, Greg KH wrote:
Ok, now that devfs is removed from the 2.6 kernel tree[1], I think it's
time to start to revisit some of the /dev naming rules that we currently
are living with[2].
To
On Thu, Jul 07, 2005 at 08:52:20PM +0100, John Mylchreest wrote:
On Wed, 2005-07-06 at 15:46 -0700, Greg KH wrote:
If we can move away from some of our devfs-like names, we stand to
reclaim a lot of memory from everyone's machines. As an example, if we
drop all of the tty/pts/vc/vcc
On Thursday 07 July 2005 22:15, Duncan wrote:
Simon Stelling posted [EMAIL PROTECTED], excerpted below, on
Thu, 07 Jul 2005 20:49:04 +0200:
Hi,
Chris White wrote:
jforman
EBUILD BUGS GO IN GENTOO LINUX PRODUCT STOP MARKING EVERY BUG AS A
BLOCKER
/jforman
What about changing
Robin H. Johnson wrote: [Thu Jul 07 2005, 05:07:06PM EDT]
On Thu, Jul 07, 2005 at 04:49:13PM -0400, Aron Griffis wrote:
Current (possibly unwritten) policy:
- eclasses declare USE-flags they honor in their own IUSE
- ebuilds declare USE-flags they honor in their own IUSE
- ebuilds
On Thu, 7 Jul 2005, Robin H. Johnson wrote:
The only official ways to use USE flags are (at least to my knowledge):
use FLAG
usev FLAG
useq FLAG
use_enable FLAG
use_with FLAG
I don't think I'm missing any here am I?
It's a little harder because use $variable is valid and used in ebuilds
as
On Thursday 07 July 2005 04:49 pm, Aron Griffis wrote:
Current (possibly unwritten) policy:
- eclasses declare USE-flags they honor in their own IUSE
- ebuilds declare USE-flags they honor in their own IUSE
- ebuilds do not declare USE-flags honored by eclasses they inherit
err this
On Thursday 07 July 2005 07:11 pm, Daniel Drake wrote:
Any comments?
does fbsplash work for all the same kernels bootsplash does ? if so i dont
see why punting it would be a problem ...
-mike
--
gentoo-dev@gentoo.org mailing list
On Thu, 2005-07-07 at 13:52 -0700, Greg KH wrote:
On Thu, Jul 07, 2005 at 03:55:45PM +0200, Martin Schlemmer wrote:
On Wed, 2005-07-06 at 15:46 -0700, Greg KH wrote:
Ok, now that devfs is removed from the 2.6 kernel tree[1], I think it's
time to start to revisit some of the /dev naming
Vapier wrote: [Thu Jul 07 2005, 06:13:06PM EDT]
On Thursday 07 July 2005 04:49 pm, Aron Griffis wrote:
Current (possibly unwritten) policy:
- eclasses declare USE-flags they honor in their own IUSE
- ebuilds declare USE-flags they honor in their own IUSE
- ebuilds do not declare
On Thu, 2005-07-07 at 20:28 +0200, Maurice van der Pot wrote:
On Thu, Jul 07, 2005 at 10:52:06AM -0700, Donnie Berkholz intended to write:
size for the options above 0.05%, 0.02% and 0.01% respectively. In
any case, nearly irrelevant to its present size.
Mixed up my decimal points and
41 matches
Mail list logo
