-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Peter Pentchev schrieb:
> As Paul Wise said, the removing would be a good idea if the packager
> is not completely certain that the upstream build system will never,
> ever, under any circumstances, use the bundled source even if it is
> told to use the external libraries. Consider a build system that goes
> like, "Oh, okay, you told me to use the external library, but something
> changed, I can't quite locate the header file, or this definition is
> no longer available, or something just messed up... no matter, if I
> can't use the external library, I'll just use my own source, I *know*
> things will build just fine this way!". Honest, I've seen upstream
> sources that did that.
Isn't this something the maintainer should check before he uploads his
package?
- --
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
Comment:
Always if we think we are right,
we were maybe wrong.
*/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkp/NGAACgkQ2XA5inpabMeKlwCcClIpQkiinlVPm+4TxXSvr1Zk
eOwAn36P7dtFpg4cHeIhAxxTMYQdw7Wz
=Rt4n
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
