Bug#714634: [lsb-discuss] Clarification of general LSB requirements

Steve Langasek <[email protected]> Wed, 10 Jul 2013 17:25:40 -0700
Newsgroups gmane.linux.debian.devel.lsb
Message-ID <20130711002540.GA10231__33271.9468897723$1373502445$gmane$org@virgil.dodds.net>
On Wed, Jul 10, 2013 at 12:08:00PM -0700, Russ Allbery wrote:
> > I would argue that lsb-invalid-mta is a perfectly valid solution for
> > lsb-core, but that it should not Provide: mail-transport-agent - so that
> > any packages that actually say "yes, I require an MTA" get the default
> > MTA and not the lsb-invalid-mta bodge.

> Yeah, I agree with this, and also that lsb-core should actually depend on:

>     default-mta | mail-transport-agent | lsb-invalid-mta

> to achieve this so that lsb-invalid-mta isn't the default choice.  I think
> that's separate than the more general standards issue under discussion
> here (it still wouldn't prohibit the installation of lsb-core with
> lsb-invalid-mta), but I think that change would be a quality of
> implementation improvement in the LSB package.

If lsb-core is going to pull in default-mta as the preferred option, then
arguably lsb-invalid-mta shouldn't exist at all (or at least, there's no
reason to label it an 'lsb' package).  I think the purpose of the package is
to let lsb-core be installed without automatically pulling in an MTA that
has to be configured, and default-mta | mail-transport-agent | lsb-invalid-mta
wouldn't achieve that.

But I think dropping the Provides: from lsb-invalid-mta would.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
[email protected]                                     [email protected]
signature.asc (application/pgp-signature, 836 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJR3fuEAAoJEFaNMPMhshM9WLgQAJ1UVxalU9+4PEYSwRQEvGAl
jzexXL8VJ0WgOgwowLYBC23QaUH7tLxi34Fpxww9WLs4chp6T3F/blkT3g5zQusF
Z3A3QpGw7ZwugOeKnIVbArEQzcgyCao8nf/5Iju7aB94O+yL0gdzIAF2rr/wI6aN
aIrtDLy9ivqCSAu9ERC0let5qRSIpwO2fmd2kCKdNrKakHOAN+C/vpEVn0ygxnDI
1YCcUI9xr3nX6Jh3opKZ2HIlLfMWcG+xu0ntdzygu3JjueT0KGI8mr2DtFi4r1mL
fL1oVeMzWBx+/HGM6FNj8MMmkbz4Y9RhZZJ6J71KLv4GAbH5CQKFUamx1vAtvVvL
FiC3eZDZ7NSiNBzqIMVP+iV97u3BPwbemYKE7+1Cx5/2mZb0/PMsswOLxyR+yC6c
2NPHcxOj1jC8jmPLGo3U0ulEqd6kVB4Glxj8agdk0Pm4AUqXlqNaYGGnC+cUljE9
reOUpIo0p1R6Ris9hrvTHKrgyoFsDJbTMc051Jwyreclu5oYBR0yZRqBWFsEm5Wd
h2ML1JIlcS6WL16o9pZhzr+fYHV4vKdVFYsY/sBgJIZYZz2jDAGa4NzoJNNsN3QY
XZ7B0KqMT6bLZqgflbw3+CZ2+w7hw5TqTyYMEqNxP6j+s+Cl1yytGJUf3349as7+
Qu3vlVrfY/PlCc9hTA+K
=SvOM
-----END PGP SIGNATURE-----