1 |
On Mon, 2007-10-01 at 16:06 -0700, Donnie Berkholz wrote: |
2 |
> On 19:16 Mon 01 Oct , Sébastien Fabbro wrote: |
3 |
> > On Sun, 2007-09-30 at 13:53 -0700, Donnie Berkholz wrote: |
4 |
> > > > 1.1 dev-lang/ifc/ifc-10.0.026.ebuild |
5 |
> > |
6 |
> > > > INSTALL_DIR=/opt/intel/${PB}${ext}/${PV} |
7 |
> > > > |
8 |
> > > > if use debugger && [[ ! -x /opt/intel/idb${ext}/${PV}/bin/idb ]]; then |
9 |
> > > > INSTALL_IDB_DIR=/opt/intel/idb${ext}/${PV} |
10 |
> > > > else |
11 |
> > > > use debugger && einfo "Debugger already installed" |
12 |
> > > > rm -f data/intel*idb*.rpm |
13 |
> > > > fi |
14 |
> > > |
15 |
> > > Could you explain what this is doing? Does some other package (icc?) |
16 |
> > > also install the debugger? Perhaps it should get split off into a |
17 |
> > > separate package. |
18 |
> > |
19 |
> > Yes, icc can install the same debugger. I thought about splitting idb in |
20 |
> > another package but it would need either the ifc or the icc tar ball. I |
21 |
> > thought the "or" was not supported in SRC_URI/unpack. Forcing the tar |
22 |
> > ball of icc would force the ifc users to download icc one (at least |
23 |
> > 40Mb) when not necessary, and vice-versa. There are probably solutions |
24 |
> > to this problem, but I could not think of a simple one. Any suggestion |
25 |
> > welcome. |
26 |
> |
27 |
> As kind of a hack solution, the idb package could have icc/ifc USE flags |
28 |
> to pick which tarball it used. |
29 |
|
30 |
I have been trying to avoid the icc/ifc use flags as much as possible, |
31 |
in preference for things like [[ $(tc-getCC) = icc ]] but in that case |
32 |
it would make sense. |
33 |
|
34 |
Thanks. |
35 |
|
36 |
Sébastien |