[prev in list] [next in list] [prev in thread] [next in thread] 

List:       crux
Subject:    Re: pcmcia-cs port trouble
From:       Florian Weber <Florian.Weber () pfaffenhofen ! de>
Date:       2002-08-01 2:13:42
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 25 July 2002 10:12, Mikael Bak wrote:
> When you build pcmcia-cs it checks your kernel configuration (.config) to
> see if you have included any pcmcia drivers (modules). If not, the
> pcmcia-cs package will compile its own modules. If yes, it'll use the
> default kernel pcmcia modules.
> In either case your .footprint file will depend on how you have configured
> your kernel.
>
> How should I cope with this problem?
> My first reaction was to skip the .footprint file from the port
> distribution, but that might not be a good idea.
> What do you guys think?

The 'correct' solution seems to be to put sections into the footprint that say 
"those (sets of) files are mutually exclusive, but one of them must be 
present". 
Of course, this is utter nonsense when applied to CRUX.

If you keep the footprint, you will get a build error in most cases. A CRUX 
user should be able to quickly recognize and resolve the problem (perhaps put 
a small README with the port?). On the other hand, with the footprint you'll 
be able to recognize if *really* important files are missing - which is 
impossible without a footprint.

So I'd say include the footprint and let everybody deal with the consequences. 

- -- 
With best regards,
Florian Weber

PGP key ID: 3C4E74DC
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9SJlWm8fasDxOdNwRAm3JAJ9Id8e9rH0RAe6dEyeWFwg/nk1huACeKrvv
65i4Ep3BsJpsQGIWm7xdCac=
=SdOp
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]