question on policy
-----BEGIN PGP SIGNED MESSAGE-----
I have a question which seems not to be covered by the policy or
programmer's manual (feel free to correct me on that). I have a program
that I want package (xirc for the curious) that comes with a source for
the static library. After the library is generated, the binary is
statically linked with that library. My question is: What should I do
with the library and its source?
I see several options:
1) include it in the source, and include its compilation at build time (in
the rules)
2) Release it as a separate package
3) only include the compiled library in the source.
4) do 1) or 3) and include the library itself in the package.
Which way should I go? It seems to me that 3 and 4 are not good options,
but I wanted to include them just in case.
__
Proudly running Debian Linux! Linux vs. Windows is a no-Win situation....
Igor Grobman igor@vaca.net
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv
iQBVAwUBMwxHZf6MRr9c8VylAQGjDwH9FNekSU78QwtS+KAUft4UCS9B1uwPffXn
0YYnif+Q8MIrZ5fLJ8nMsUgIpVr4kebyLuQtAsBWeHz0XrKNsLZHwA==
=48W7
-----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 Bruce@Pixar.com
Reply to: