On Saturday 27 August 2005 03:38 pm, Martin Schlemmer wrote:
On Sat, 2005-08-27 at 15:11 -0400, Mike Frysinger wrote:
On Saturday 27 August 2005 02:58 pm, Martin Schlemmer wrote:
Which reminds me .. anybody going to scream if I update elibtoolize()
to be able to check if it was already
Donnie Berkholz wrote:
Brian Harring wrote:
I don't recall having kde/gtk crap turned on by default when I first
showed up. Maybe I'm missing something; regardless, the defaults
(which should be minimal from my standpoint) are anything but.
I think you recall wrong, then. The default USE
On Sun, 2005-08-28 at 01:59 -0400, Mike Frysinger wrote:
On Saturday 27 August 2005 03:38 pm, Martin Schlemmer wrote:
On Sat, 2005-08-27 at 15:11 -0400, Mike Frysinger wrote:
On Saturday 27 August 2005 02:58 pm, Martin Schlemmer wrote:
Which reminds me .. anybody going to scream if I
On Sun, 2005-08-28 at 12:01 +0200, Simon Stelling wrote:
Donnie Berkholz wrote:
Brian Harring wrote:
I don't recall having kde/gtk crap turned on by default when I first
showed up. Maybe I'm missing something; regardless, the defaults
(which should be minimal from my standpoint) are
On Sunday 28 August 2005 07:28 am, Martin Schlemmer wrote:
On Sun, 2005-08-28 at 01:59 -0400, Mike Frysinger wrote:
On Saturday 27 August 2005 03:38 pm, Martin Schlemmer wrote:
On Sat, 2005-08-27 at 15:11 -0400, Mike Frysinger wrote:
On Saturday 27 August 2005 02:58 pm, Martin Schlemmer
I must say I have been wondering about this for a while too.
A solution might be add some sort of flag to packages that are binary,
and then let portage install libstdc++ the first time you install this
kind of package.
You mean, like have binary packages depend on
On Sun, 2005-08-28 at 12:50 -0400, Mike Frysinger wrote:
On Sunday 28 August 2005 07:28 am, Martin Schlemmer wrote:
On Sun, 2005-08-28 at 01:59 -0400, Mike Frysinger wrote:
On Saturday 27 August 2005 03:38 pm, Martin Schlemmer wrote:
On Sat, 2005-08-27 at 15:11 -0400, Mike Frysinger
On Sunday 28 August 2005 01:43 pm, Martin Schlemmer wrote:
On Sun, 2005-08-28 at 12:50 -0400, Mike Frysinger wrote:
On Sunday 28 August 2005 07:28 am, Martin Schlemmer wrote:
On Sun, 2005-08-28 at 01:59 -0400, Mike Frysinger wrote:
On Saturday 27 August 2005 03:38 pm, Martin Schlemmer
On Sun, 2005-08-28 at 13:54 -0400, Mike Frysinger wrote:
On Sunday 28 August 2005 01:43 pm, Martin Schlemmer wrote:
On Sun, 2005-08-28 at 12:50 -0400, Mike Frysinger wrote:
On Sunday 28 August 2005 07:28 am, Martin Schlemmer wrote:
On Sun, 2005-08-28 at 01:59 -0400, Mike Frysinger wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
since there has been a lot of discussion lately about default use flags,
I looked at the profiles and found the following:
All of these use flags are in base/use.defaults. As I understand it, if
the package listed with the flag in this file is
On Sunday 28 August 2005 03:36 pm, William Hubbs wrote:
All of these use flags are in base/use.defaults. As I understand it, if
the package listed with the flag in this file is installed on the
system, the flag is automatically turned on. If that's true, why are
they also listed in
I am writing an ebuild and wishing to use make_desktop_entry
I have two problems with it:
1. the resulting desktop file is called laby-laby.desktop rather than
just laby.desktop
2. the Comment in the desktop file says Comment=Based on the eutils eclass
1. I am unable to work out at all, except
On Sunday 28 August 2005 09:42 pm, Nick Rout wrote:
1. the resulting desktop file is called laby-laby.desktop rather than
just laby.desktop
the name doesnt matter just ignore it
2. the Comment in the desktop file says Comment=Based on the eutils
eclass
your ebuild is using 'inherit'
On Sun, Aug 28, 2005 at 02:31:24AM -0700, Zac Medico wrote:
Brian Harring wrote:
Please test this out; if you want to test the EAPI checking, tag
EAPI=1 into an ebuild, and try making emerge bail.
I needed to patch ebuild.sh so that EAPI would be parsed. It bails out
properly now.
Crud,
14 matches
Mail list logo
