On Wed, 19 Jun 2013 19:00:54 +0200, Ralf Jung <p...@ralfj.de> wrote: > > It would be great if the osspd package could blacklist the OSS > > modules... All it takes is dropping the attached file in the debian > > directory, dh_installmodules picks it up automatically. > Thanks for the patch. I will prepare a new upload soon (during the > week-end, probably) and notify my sponsor. > > > BTW oss-compat now recommends osspd on Linux architectures. > Nice :) > On the other hand, osspd has > Conflicts: oss-compat > Provides: oss-compat > I added this because installing oss-compat blocks osspd from starting, > it reserves the kernel major/minor numbers (or the device name, not sure > which is more significant). Probably, after adding the blacklist, I > don't need this "Conflicts" anymore? > I added the "Provides" to keep bb (and other packages requiring > oss-compat) installable, so this could also be removed if the > "Conflicts" is no longer needed. I have no strong preference on how > these relations are handled, as long as it is possible to have bb (and > others) installed with a working osspd.
I saw the conflicts/provides; that's what prompted me to update oss-compat
and start preparing an upgrade path to osspd (as far as I'm concerned osspd
is the correct upgrade path for oss-compat on platforms where it's
available).
With the blacklist, and the changes to oss-compat 3, you shouldn't need to
conflit with oss-compat, so osspd could just "provide" oss-compat and I could
actually have oss-compat depend on osspd, which would ensure users actually
got pushed to osspd. That would make a whole lot of Ubuntu users happy, and I
dare say a few Debian ones as well... Strictly speaking osspd needs to
declare "Conflicts: oss-compat (<= 2)" to avoid breakages related to
oss-compat 2's incorrect modules configuration.
So if you change osspd to
Provides: oss-compat
Conflits: oss-compat (<= 2)
I'll happily change oss-compat to
Depends: osspd [linux-any]
Regards,
Stephen
signature.asc
Description: PGP signature
