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/Al
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 wi
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 a
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.
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 passwd backends
> listsed in /etc/nsswitch.conf. However, i
On Fri, 16 Jun 2006 12:16:52 +0200
"Diego 'Flameeyes' Pettenò" <[EMAIL PROTECTED]> wrote:
> 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
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 al
Hi,
A quick note for those who have not heard about it already:
We are hosting a users-and-developers conference in Central London on
July 8th. Anyone interested in Gentoo is welcome to attend.
The day will consist of presentations and sessions run by Gentoo
developers, plus one or two from
Chris Gianelloni wrote:
> Most things *should* not to *anything* if the account exists in
> mysql/ldap/nis/etc as the account is already present.
Right, i.e. use NSS for the query and *don't* use hacks like grepping
/etc/passwd.
> It's just the
> case of it *not* existing that causes the real pr
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 wi
What about gcc-config - will that work?
>
> From: Sven Köhler <[EMAIL PROTECTED]>
> Date: 2006/06/16 Fri PM 03:10:08 EDT
> To: gentoo-dev@lists.gentoo.org
> Subject: [gentoo-dev] using specific gcc-version in ebuild
>
>
--
gentoo-dev@gentoo.org mailing list
On Friday 16 June 2006 15:10, Sven Köhler wrote:
> 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.*)?
no, there isn
-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.* ve
Yeah, I missed the context! I was not thinking about an ebuild.
>
> From: Joshua Jackson <[EMAIL PROTECTED]>
> Date: 2006/06/16 Fri PM 03:31:32 EDT
> To: gentoo-dev@lists.gentoo.org
> Subject: Re: [gentoo-dev] using specific gcc-version in ebuild
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash:
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 t
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 Fri, 16 Jun 2006 15:30:06 -0400
Mike Frysinger <[EMAIL PROTECTED]> wrote:
> On Friday 16 June 2006 15:10, 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 t
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 develope
Alec Warner wrote:
So apparently they suck, anyone have a new shiny idea on how to group
packages and maintaining developers?
Sure -- take the current herds implementation, and rename it to 'gaggle'! Then
we can call things the base-system gaggle, the toolchain gaggle, etc...
Even metadata.
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 previous
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 "${FILESDIR}/some-
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 "${FILESDIR}/some
On Sat, 17 Jun 2006, 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 309
Thomas Cort <[EMAIL PROTECTED]> wrote:
> What is the proper quoting style for using epatch? In the tree there
> are about 3 different styles...
> What is the proper quoting style for defining the S variable? In the
> tree there are about 3 different styles...
It might be prudent to quote the varia
Harald van D??k <[EMAIL PROTECTED]> wrote:
> Any is fine, there is no word splitting or wildcard expansion in
> shell variable assignments.
$ foo="bar * baz"
$ wombat=$foo
$ echo $wombat
bar somedir somefile baz
--
^
^
On Fri, Jun 16, 2006 at 11:31:27PM -0700, Drake Wyrm wrote:
> Harald van D??k <[EMAIL PROTECTED]> wrote:
> > Any is fine, there is no word splitting or wildcard expansion in
> > shell variable assignments.
>
> $ foo="bar * baz"
> $ wombat=$foo
> $ echo $wombat
> bar somedir somefile baz
The w
29 matches
Mail list logo
