Re: source dependencies
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, 29 Jul 1997, Juergen Menden wrote:
> good, but that was not my question. the question was: can you
> give a general procedure to decide which packages some source
> depends on? if you try to be complete you will have to have the
> complete list to remove all "asumed-to-be-present" things.
Can you give a general procedure to decide that a program has no bugs?
We don't even have a general procedure for *binary* dependencies (yes, we
have the dpkg-shlibdep procedure, but this does not cover all
dependencies), but we have a bug tracking system so if we miss some
dependency, sooner or later we (or some user) should discover it.
I don't see great difference between source and binary dependencies.
So I don't see the need to use any other word than "Depends:".
Thanks.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
iQCVAgUBM927ESqK7IlOjMLFAQFZ5QP+Ot8vB+Kk5DwtHvbY44iXaGryog9qqoA8
IYMweEf8ZbfJ7BgdHlWKgjTsrZI9oQAR3S1Vg99DUXkfXEq3vVny+0SD7Li+bO9l
VCQKQd3GpuvDrn6sLmijwXvYJC30Wlrp+maJlUxuksSlFcWk04EA+R2LfPynsU2t
mgEVZV4ouUs=
=bDv/
-----END PGP SIGNATURE-----
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: