Using masked packages in Catalyst .spec file

Branched from a question to Chris regarding using masked
packages when
building a minimal CD.

> > Hi,
> >
> > I'm trying to build my own version of the 2006.0
minimal CD with
> > madwifi support (I realize that madwifi is
unstable). I've added a
> > madwifi to the use flag section and madwifi-driver
to the package
> > section. I can't run "catalyst -f
livecd-stage1-minimal-madwifi.spec"
> > though since madwifi-driver is masked (error
attached below). How do I
> > unmask a package for the build?
>
> You cannot.  You need to unmask it in your snapshot, or
use
> portage_overlay to create a portage overlay.

I found a portage_confdir variable in one of the .spec file
that I can
have point at a package.keywords file. Can you confirm that
this is a
way to use masked packages?
-- 
gentoo-catalystgentoo.org mailing list

Johan Tibell wrote:
> Branched from a question to Chris regarding using
masked packages when
> building a minimal CD.
> 
>> > Hi,
>> >
>> > I'm trying to build my own version of the
2006.0 minimal CD with
>> > madwifi support (I realize that madwifi is
unstable). I've added a
>> > madwifi to the use flag section and
madwifi-driver to the package
>> > section. I can't run "catalyst -f
livecd-stage1-minimal-madwifi.spec"
>> > though since madwifi-driver is masked (error
attached below). How do I
>> > unmask a package for the build?
>>
>> You cannot.  You need to unmask it in your
snapshot, or use
>> portage_overlay to create a portage overlay.
> 
> I found a portage_confdir variable in one of the .spec
file that I can
> have point at a package.keywords file. Can you confirm
that this is a
> way to use masked packages?

You can use this method, however, it is probably better just
to remove the mask 
in your snapshot.

-- 
Andrew Gaffney                            http://dev.gentoo.or
g/~agaffney/
Gentoo Linux Developer                                  
Installer Project

-- 
gentoo-catalystgentoo.org mailing list

On Fri, 2006-08-25 at 20:36 +0200, Johan Tibell wrote:
> Branched from a question to Chris regarding using
masked packages when
> building a minimal CD.
> 
> > > Hi,
> > >
> > > I'm trying to build my own version of the
2006.0 minimal CD with
> > > madwifi support (I realize that madwifi is
unstable). I've added a
> > > madwifi to the use flag section and
madwifi-driver to the package
> > > section. I can't run "catalyst -f
livecd-stage1-minimal-madwifi.spec"
> > > though since madwifi-driver is masked (error
attached below). How do I
> > > unmask a package for the build?
> >
> > You cannot.  You need to unmask it in your
snapshot, or use
> > portage_overlay to create a portage overlay.
> 
> I found a portage_confdir variable in one of the .spec
file that I can
> have point at a package.keywords file. Can you confirm
that this is a
> way to use masked packages?

You *can* but it isn't really advised.  The best way really
is via the
snapshot, with the overlay as the second best, and confdir a
distant
last.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux