From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Glibc, non-glibc and external libs
Date: Thu, 16 Jun 2005 09:14:39 -0400 [thread overview]
Message-ID: <200506160914.39413.vapier@gentoo.org> (raw)
In-Reply-To: <200506160633.33410@enterprise.flameeyes.is-a-geek.org>
On Thursday 16 June 2005 12:33 am, Diego 'Flameeyes' Pettenò wrote:
> On Thursday 16 June 2005 06:22, Mike Frysinger wrote:
> > tracking packages which need getopt is a waste of time, just force it in
> > your profile/bsd libc/whatever
>
> it's not getopt, it's getopt_long... which is used by few packages.
> well actually freebsd provide it in library in latest releases, aslo if
> it's developed on its own... maybe I can hack a bit the build process to
> have this external as we need.
yes i know the diff between getopt and getopt_long, that doesnt change the
fact that tracking either is a waste of time
-mike
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-06-16 13:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 22:02 [gentoo-dev] Glibc, non-glibc and external libs Diego 'Flameeyes' Pettenò
2005-06-15 23:13 ` Olivier Crete
2005-06-16 2:41 ` Diego 'Flameeyes' Pettenò
2005-06-16 5:58 ` [gentoo-dev] " Duncan
2005-06-16 6:18 ` Diego 'Flameeyes' Pettenò
2005-06-16 9:26 ` Marius Mauch
2005-06-16 9:41 ` Thomas de Grenier de Latour
2005-06-16 11:14 ` Marius Mauch
2005-06-16 13:57 ` [gentoo-dev] " Chris Gianelloni
2005-06-16 4:22 ` Mike Frysinger
2005-06-16 4:33 ` Diego 'Flameeyes' Pettenò
2005-06-16 13:14 ` Mike Frysinger [this message]
2005-06-16 13:47 ` Diego 'Flameeyes' Pettenò
2005-06-16 14:13 ` Martin Schlemmer
2005-06-16 15:51 ` Diego 'Flameeyes' Pettenò
2005-06-16 16:07 ` Mike Frysinger
2005-06-16 16:28 ` Diego 'Flameeyes' Pettenò
2005-06-16 14:18 ` Marius Mauch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200506160914.39413.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox