On Mon, 13 Jun 2011, Guillem Jover wrote: > Package: dpkg-dev > Version: 1.16.0 > Severity: wishlist > User: d...@packages.debian.org > Usertags: dpkg-gensymbols > > Hi! > > It would be nice to have a private tag which would have the following > semantics: > > * any symbol marked as such could not be used by any external package, > it would produce a fatal error at dpkg-shlibdeps time. > * such symbols could be used by binary packages produced from the same > source package. > * probably they should be non-optional by default, as there's the > optional tag already, and there's no way to mark a symbol as > non-optional anyway. > > So while this could alternatively be achieved by modifying upstream > source, with one of the following methods: advanced or simple symbol > versioning, symbol visibility or an export map; it might not be always > desirable to diverge from upstream on this. So having support for > this in Debian would allow package maintainers to disallow external > dependencies on interfaces which are not supposed to be used. > > The biggest issue I see is how to transport that information from > the symbols pattern file in the source to the binary package.
Since private symbols are not to be used outside of the source package, we can just invent a special value to use in the associated minimal version field. symbol@Base *private* If that's not ok, then the easiest is to add a supplementary (optional) field/column on each symbol line. But it requires to make the dependency number explicit in the cases where it was omitted. symbol@Base 1.2-3 0 private Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
