From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Portability eclass
Date: Sat, 17 Sep 2005 15:01:08 +0200 [thread overview]
Message-ID: <200509171501.32392@enterprise.flameeyes.is-a-geek.org> (raw)
In-Reply-To: <200509161743.07528@enterprise.flameeyes.is-a-geek.org>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On Friday 16 September 2005 17:42, Diego 'Flameeyes' Pettenò wrote:
> If we'll find other functions needed for portability's sake, they'll
> probably going to be there, too.
Dropped the symcmd function, cleaned up the treecopy function (Martin, take a
look at cp --parent, what treecopy does is just the same, if someone calls it
with ${S}, it WILL create ${S} inside ${D}, but that's what they are asking
for using it), added an eseq option, that would be used on enewuser and
elsewhere were seq is used.
This does not use ${USERLAND} to find out which command to use, as Darwin can
have seq installed (and actually someone can have userland-gnu merged on *BSD
and path changed), so it just look if it's able to find seq, otherwise use
jot.
If this is ok, I'll commit this tonight changing enewuser according to use it.
--
Diego "Flameeyes" Pettenò
Gentoo Developer - http://dev.gentoo.org/~flameeyes/
(Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-09-17 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 15:42 [gentoo-dev] [RFC] Portability eclass Diego 'Flameeyes' Pettenò
2005-09-16 15:59 ` Mike Frysinger
2005-09-16 16:33 ` Diego 'Flameeyes' Pettenò
2005-09-16 17:21 ` Chris Gianelloni
2005-09-16 17:28 ` Mike Frysinger
2005-09-16 17:36 ` Diego 'Flameeyes' Pettenò
2005-09-16 17:59 ` warnera6
2005-09-16 19:12 ` Mike Frysinger
2005-09-16 16:16 ` Martin Schlemmer
2005-09-16 17:07 ` Diego 'Flameeyes' Pettenò
2005-09-17 13:01 ` Diego 'Flameeyes' Pettenò [this message]
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=200509171501.32392@enterprise.flameeyes.is-a-geek.org \
--to=flameeyes@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