Edward --
I am trying to build a package called sipXphone. It requires
glib-2.4.2, but most of my current packages require glib-2.6.3 (the
latest version). One would think that the versioning would be backwards
compatible but this is not the case. The technique I described below
doesn't work and is breaking my portage system, so I wouldn't advise
other people trying to do this. I still don't know how to proceed
except by building this old version, in a special area that doesn't
conflict with the rest of the system (ie. /usr/local). If anyone knows
how to do this using portage or could give some good reasons as to why
portage cannot do this, I would be obliged. Thanks,
--
Michael Andrews | <[EMAIL PROTECTED]>
0xE7D25F66 | keyserver.net
Edward Catmur wrote:
> Generally if two versions of an ebuild have the same SLOT, then they
> will conflict in some way (normally by installing files with the same
> name) and so having one installed will break the other.
>
> Which packages are you trying to install?
>
> On Wed, 2005-04-20 at 14:20 -0400, [EMAIL PROTECTED] wrote:
>
>>Hi,
>>
>>I am trying to install two different versions of the same package.
>>I think the SLOTS mechanism of portage can handle this, but I get the
>>feeling that this feature is only exposed to developers, and not to a user.
>>I tried following the advice given here:
>>
>>http://gentoo-wiki.com/TIP_Installing_Specific_Packages
>>
>>and this did not work.
>>In the ebuild I was trying to install I changed the SLOTS value to a new
>>number and then typed:
>>
>>ebuild foo.ebuild digest
>>
>>to remake the md5sums. This worked and the package was placed into a
>>new slot, but I feel/hope there is an easier way to do this.
>>Thanks for helping,
>>
>>
>>--
>> Michael Andrews | <[EMAIL PROTECTED]>
>> 0xE7D25F66 | keyserver.net
>>
>>
>>
>
>
--
[email protected] mailing list
