On Friday 16 June 2006 05:03, Mike Frysinger wrote:
nss is glibc-only, so such a solution would be inadequate
Actually this is one of the strange and rare cases that's not only glibc's.
FreeBSD can use nss too :)
--
Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt
On 15/06/06, Curtis Napier [EMAIL PROTECTED] wrote:
Shyam Mani wrote: Hi everyone, Please take a moment to welcome our latest addition to the Forums gang, Roy Bamford aka NeddySeagoon.Thanks for volunteering your time Roy, we will all benefit from your
extensive knowledge and your patience with
Chris Gianelloni [EMAIL PROTECTED] posted
[EMAIL PROTECTED], excerpted below, on
Thu, 15 Jun 2006 14:39:35 -0400:
On Thu, 2006-06-15 at 19:18 +0100, Stuart Herbert wrote:
Hi Kevin,
On 6/15/06, Kevin F. Quinn [EMAIL PROTECTED] wrote:
I read the should as
implying that all new packages
On Thu, 2006-06-15 at 21:36 -0400, Mike Kelly wrote:
Hi,
As part of my original plans for my GLEP27 implementation, I was
going to have my scripts automatically add the users requested by a
package (for example, the cron user), to all the passwd backends
listsed in /etc/nsswitch.conf.
On Fri, 2006-06-16 at 08:42 -0500, Grant Goodyear wrote:
Mike Kelly wrote: [Thu Jun 15 2006, 08:36:25PM CDT]
As part of my original plans for my GLEP27 implementation, I was
going to have my scripts automatically add the users requested by a
package (for example, the cron user), to all the
Hi,
i just wanted to ask, if the is an eclass or something else, that
enables me to temporarly select a certain gcc-version? or perhaps just
finding the path to the gcc and g++ executables of a specific
gcc-versions (like gcc-3.*)?
some software, like qemu and others, are simply not compatible
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Forcing a change in your gcc version for compiling is less then
optimal. I don't believe the eclass has anything in it that will help
in what you are trying to do. I would probably do a pkg_setup with a
check for the version of gcc if it isn't a 3.*
Hi folks,
I'm maintaining patches with fixes for dozens of packages for
quite some time. These patches are needed since releases are
often quite broken (ie. crosscompiling doesn't work) or there
are other things which make sysop's or distro maintainer's
life evrything but easy.
Most of the
some software, like qemu and others, are simply not compatible with gcc
4.x and they will not become compatible due to severe conceptional issues.
then they stay broken ... add a warning to the ebuild if `gcc-major-version`
is 4 (see toolchain-funcs.eclass)
Hmm, but ...
there is the
Sven Köhler wrote:
some software, like qemu and others, are simply not compatible with gcc
4.x and they will not become compatible due to severe conceptional issues.
then they stay broken ... add a warning to the ebuild if `gcc-major-version`
is 4 (see toolchain-funcs.eclass)
Hmm,
On Thu, 2006-06-15 at 00:26 -0500, Lance Albertson wrote:
Alec Warner wrote:
So apparently they suck, anyone have a new shiny idea on how to group
packages and maintaining developers?
How exactly does one go about maintaining our developers? ;)
I suggest we create a murder of developers!
Marius Mauch wrote:
Functional changes, bugfixes, etc. Let people use common sense there.
The intention is simply that people watching the bug don't have to track
the overlay as well to get notifications of important changes (like a
bugfix that prevented them from using the ebuild
What is the proper quoting style for using epatch? In the tree there
are about 3 different styles...
epatch ${FILESDIR}/some-fix.patch # used by 7326 ebuilds
epatch ${FILESDIR}/some-fix.patch# used by 3092 ebuilds
epatch ${FILESDIR}/some-fix.patch# used by
Thomas Cort wrote:
What is the proper quoting style for using epatch? In the tree there
are about 3 different styles...
epatch ${FILESDIR}/some-fix.patch # used by 7326 ebuilds
epatch ${FILESDIR}/some-fix.patch# used by 3092 ebuilds
epatch
Thomas Cort wrote:
What is the proper quoting style for using epatch? In the tree there
are about 3 different styles...
epatch ${FILESDIR}/some-fix.patch # used by 7326 ebuilds
epatch ${FILESDIR}/some-fix.patch# used by 3092 ebuilds
epatch
On Sat, Jun 17, 2006 at 12:35:30AM -0400, Thomas Cort wrote:
What is the proper quoting style for using epatch? In the tree there
are about 3 different styles...
epatch ${FILESDIR}/some-fix.patch # used by 7326 ebuilds
epatch ${FILESDIR}/some-fix.patch# used by 3092
16 matches
Mail list logo
