If you use this justification how about giving us at least a hint on how
it fails to build?
doing
m-a a-i virtualbox-ose-source
ends with the need to install unnecessary packages, which in turn would
modify my system against my will (i don't want any prebuild kernels on my
system) which means imo it breaks.
i consider a run of m-a a-i as a full build -- and if it is unable to
accomplish this task for reasons caused by the package it is a bug.
but that might be hairsplitting ...
it is a major nuisance that a lot of those source packages depend on
They do not.
well, the source creates packages that do -- where, would you say, is the
dependency to locate?
that dependency does not have any justification in code nor in usability
-- it seems to be there only to annoy.
A statement like this makes me wonder if you're really here to report a
bug. There certainly is a justification.
so, please, tell me!
i am using for debian for about ten years now without ever really using
prebuild kernels -- and over time the number of
kernel-module-source-packages that created silently packages with
dependencies to prebuild kernel-module-packages seems only to grow. but
none of those packages i encountered ever needed those dependencies.
at least it should be possible to inform the user before actually
building that those packages are not installed and even better ask him,
Why? You don't need them to build. So you might even build for a
different system.
because i always have to check the source and to remove the line that says
"Depends: linux-modules-??? | linux-image-???".
as said before: the packages built work perfectly well without those
dependencies -- so, what are they there for?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
