hi,

this bug was originally filed against debian-policy, Chris Waters pointed out
that policy already discusses update-alternatives, and later on Josip Rodin
reassigned the bug to developers-reference.

now, it's true that devref does not discuss update-alternatives, but it's also
not clear to me that it should, given that it's already covered in policy. what
more could be usefully said in devref that's not already in policy? perhaps
there is some value in merely mentioning the existence of update-alternatives
and linking to the relevant section in policy? or should we just mark this as
wontfix?

thanks,
serafi

Attachment: signature.asc
Description: PGP signature

Reply via email to