[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Unidentified subject!

X-Mailer: emacs (via feedmail 8 I)
X-Hashcash: 1:23:070110:debian-mentors@lists.debian.org::UkzcTxrtVnlskpr5:000000000000000000000000000000VaZr
From: Hubert Chan <uhoreg@debian.org>
To: debian-mentors@lists.debian.org
Subject: Re: Library sonames and unstable libraries
References: <20070105175617.GS14637@urchin.earth.li>
Date: Tue, 09 Jan 2007 22:13:26 -0500
In-Reply-To: <20070109114127.GS14637@urchin.earth.li> (Dominic Hargreaves's
	message of "Tue, 9 Jan 2007 11:41:27 +0000")
Message-ID: <8764bfy3op.fsf@evinrude.uhoreg.ca>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Tue, 9 Jan 2007 11:41:27 +0000, Dominic Hargreaves <dom@earth.li> said:


> Assuming that I want to publish some at least partially useful
> packages (for a start, much of the use will be via python bindings
> rather than linking against the .so) until upstream has committed to
> an soname policy, and made a stable release, would it be acceptable to
> use experimental for this (ie where the package is otherwise
> policy-clean but doesn't have clean soname bumps during the tracking
> of SVN snapshots) or should I stick to having this in my private
> webspace (and losing autobuilding, bugtracking and other bits and
> pieces of functionality)?

I believe that packages in experimental must still follow policy, so you
shouldn't use experimental unless you figure out how to handle the
sonames.  If use will be limited to the Python bindings, you may be able
to get away with making the C libraries private and sticking them in
/usr/lib/mapnik, at least for now.  (And, you would probably skip out on
the -dev package.)

Otherwise, your options are probably to just use your own private
webspace, or make the library into a static library.

Hubert Chan <uhoreg@debian.org> -- Jabber: hubert@uhoreg.ca
PGP/GnuPG key: 1024D/124B61FA         http://www.uhoreg.ca/
Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA

Reply to: