Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Thu, Sep 25, 2003 at 11:51:53AM +0200, Martin Lesser wrote:
> I use sys-libs/db-4.1.24.ebuild without problems and put it into my
> local ebuilds-tree where I marked it as stable (KEYWORDS="x86"). I also
> want to use db-4.1.X in SLOT="4" (instead of "4.1") for sys-libs/db so I
> don't have to play with the current 4.0.14-release. Additionally I put
> >=sys-libs/db-4.1.20
> into /etc/portage/package.unmask
I'd strongly advise against changing those SLOTs. There are some
packages that specificly want db-4.0 and others that want db-4.1.
The packages co-exist perfectly fine. I have them installed on several
servers for OpenLDAP 2.1 support.
sys-libs/db-4.1 is NOT masked in packages.mask, so putting it into
package.unmask is not the correct way of getting it released.
I have a copy in my local overlay that changes KEYWORDS to x86.
I do note that the behaviour has changed recently, I don't know why.
emerge -p '>=sys-libs/db-4.1*'
...
!!! all ebuilds that could satisfy ">=sys-libs/db-4.1" have been masked.
Carpaski: did the behaviour of the masking change some?
--
Robin Hugh Johnson
E-Mail : robbat2@...
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ# : 30269588 or 41961639
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
|
|
