From: "Christopher Chan" <cchan@spikesource.com>
To: <gentoo-osx@lists.gentoo.org>
Subject: Re: [gentoo-osx] [PREFIX] More prefixed ebuilds
Date: Mon, 24 Apr 2006 21:20:26 -0700 [thread overview]
Message-ID: <001601c6681f$95127ed0$491610ac@cardigan> (raw)
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
That sounds good Kito. I don't know if it had been discussed before, but I
was thinking it might be a good idea to create a prefix.eclass that can
share a set of functions. One function I was thinking of was to prepend the
EPREFIX, and have a smart enough to not add it if it already existed. It
seems like much of the work is figuring out where to add and where not to
add. It could give some sort of warning if the prefix was already there so
we know about it, yet does not break to build.
Thoughts on this idea?
- Chris
[-- Attachment #2: Type: text/html, Size: 2167 bytes --]
next prev reply other threads:[~2006-04-25 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 21:20 [gentoo-osx] [PREFIX] More prefixed ebuilds Christopher Chan
2006-04-25 0:22 ` Kito
2006-04-25 4:20 ` Christopher Chan [this message]
2006-04-25 7:13 ` Grobian
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='001601c6681f$95127ed0$491610ac@cardigan' \
--to=cchan@spikesource.com \
--cc=gentoo-osx@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