From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-lang/ifc: metadata.xml ChangeLog ifc-10.0.026.ebuild
Date: Mon, 1 Oct 2007 16:06:04 -0700 [thread overview]
Message-ID: <20071001230604.GZ28813@supernova> (raw)
In-Reply-To: <1191262586.5526.16.camel@zeca-laptop>
On 19:16 Mon 01 Oct , Sébastien Fabbro wrote:
> On Sun, 2007-09-30 at 13:53 -0700, Donnie Berkholz wrote:
> > > 1.1 dev-lang/ifc/ifc-10.0.026.ebuild
>
> > > INSTALL_DIR=/opt/intel/${PB}${ext}/${PV}
> > >
> > > if use debugger && [[ ! -x /opt/intel/idb${ext}/${PV}/bin/idb ]]; then
> > > INSTALL_IDB_DIR=/opt/intel/idb${ext}/${PV}
> > > else
> > > use debugger && einfo "Debugger already installed"
> > > rm -f data/intel*idb*.rpm
> > > fi
> >
> > Could you explain what this is doing? Does some other package (icc?)
> > also install the debugger? Perhaps it should get split off into a
> > separate package.
>
> Yes, icc can install the same debugger. I thought about splitting idb in
> another package but it would need either the ifc or the icc tar ball. I
> thought the "or" was not supported in SRC_URI/unpack. Forcing the tar
> ball of icc would force the ifc users to download icc one (at least
> 40Mb) when not necessary, and vice-versa. There are probably solutions
> to this problem, but I could not think of a simple one. Any suggestion
> welcome.
As kind of a hack solution, the idb package could have icc/ifc USE flags
to pick which tarball it used.
Thanks,
Donnie
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-01 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Ibw8L-0000pK-D6@stork.gentoo.org>
2007-09-30 20:53 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-lang/ifc: metadata.xml ChangeLog ifc-10.0.026.ebuild Donnie Berkholz
2007-10-01 18:16 ` Sébastien Fabbro
2007-10-01 23:06 ` Donnie Berkholz [this message]
2007-10-02 8:05 ` Sébastien Fabbro
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=20071001230604.GZ28813@supernova \
--to=dberkholz@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