Re: Policy exceptions?
On Tue, Feb 10, 1998 at 05:51:45PM +0100, Luis Francisco Gonzalez wrote:
> Hi,
> I have been pondering something similar. DMALLOC, is a malloc debugger library.
> When I took over the package I split it in two, a shared library and the
> corresponding development kit but in all honesty and with hindsight I think
> this is just wrong. There is never going to be a reason for creating packages
> that depend on a dmalloc shared library other than dmalloc itself. So the
> question is, should I join everything back into one package and ignore the
> policy in this case?
No. I don't think that you can be sure that noone ever will use your library
for other programs it is designed for. The simplest cases:
-someone creates another interface for the same task with the same library
(e.g. X gui)
-someone writes a program which uses a helper function from the lib, just
for convenience.
I think that there are good reasons for this policy. If you don't think so,
go to debian-policy and make a proposal.
---
GNU GPL: csak tiszta forrásból
--
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: