On Wed, 26 Sep 2007 01:03:38 +0200, Bastian Blank <[EMAIL PROTECTED]> said:
> On Wed, Sep 26, 2007 at 08:44:50AM +1000, Hamish Moffatt wrote:
>> It would be consistent with m-a's handling of
>> build-essential. However, I think m-a should depend on
>> build-essential since it always requires it. Therefore we are still
>> undecided about bzip2.
> m-a don't need build-essential. It needs the compiler (nothing else
> like libc headers) for the kernel. The debian linux headers already
> depends against the correct compiler.
Not good enough. What if I am using m-a with kernel.org kernel
sources? I won't have a kernel-headers package installed (I don't). If
you need something, depend upon it. Don't depend on some package you
do not even depend upon to transitively provide you with stuff; the
package you are blithely dependent upon might change its dependencies,
and your package will be up the creek without a paddle.
m-a works just fine to help me compile third party modules with
locally compiled kernels. So, if it needs bzip2, it should depend on
bzip2.
manoj
--
To use violence is to already be defeated. Chinese proverb
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
