| 1 |
On Thursday 16 September 2004 00:30, Stuart Herbert wrote: |
| 2 |
|
| 3 |
> Yes, the package would have to appear in two categories. The common |
| 4 |
> parts of the ebuild can be moved into an eclass. I'm not sure what |
| 5 |
> conflict you think will arise. All mods that support both apache1 and |
| 6 |
> apache2 should install into SLOT=1 for apache1 and SLOT=2 for apache2. |
| 7 |
|
| 8 |
I have to agree with Doug, it is not clean at all. I really would like to |
| 9 |
see some better solution than this cludge. |
| 10 |
|
| 11 |
> |
| 12 |
> > Heck.... every package... like |
| 13 |
> > emerge mod_perl wouldn't even work.. it'd give you an ugly message |
| 14 |
> > saying which one? www-apache1/mod-perl or www-apache2/mod-perl... Not |
| 15 |
> > ideal in my book. There's got to be a better way about this. |
| 16 |
> |
| 17 |
> You'd only get that message if you typed 'emerge mod_perl'. If you |
| 18 |
> typed 'emerge www-apache1/mod_perl', then you wouldn't get the message. |
| 19 |
> |
| 20 |
> As I say, I'm open to suggestions. |
| 21 |
|
| 22 |
Here indeed is a limitation in portage. |
| 23 |
|
| 24 |
Paul |
| 25 |
|
| 26 |
-- |
| 27 |
Paul de Vrieze |
| 28 |
Gentoo Developer |
| 29 |
Mail: pauldv@g.o |
| 30 |
Homepage: http://www.devrieze.net |
Archives