On Thu, Oct 09, 2008 at 10:34:34PM +0200, Loïc Minier wrote:
> I discussed this package with Kees, and I thought that the best way to
> go forward was to merge your two works and push it ASAP, and then work
> all three together via some VCS for the subsequent updates.
>
> I did the first part tonight, and will push a -3 to NEW really soon
> (see below).
Thanks for doing all this work. Regarding the patch from Kees, I'd like
to keep the static libs. They are installed side by side with the shared
ones and would be only used if explicitely requested by the developer.
> Gregor, would you be happy hosting the packaging of libv4l in some VCS,
> probably on alioth? Most VCSes are available. Kees said he would be
> fine if we were using bzr. I don't frankly care between SVN/bzr/git.
> What VCS would you prefer?
>
> The "collab-maint" project provides a good place to host packaging for
> us; Kees and I are automatically members, and we only need to add your
> Alioth account when you have one. Is this a good place for you?
Kees, I know basic things about git but get lost really fast if things
gets somemore special. Upstream uses mercurial but I don't know enough
about it to benefit from this. I have the feeling that nowadays everyone
migrates to git. But If you know bzr well enough, then let it be bzr.
As I mentioned before, I'm on holidays and will have (almost) no
internet access till next saturday. I'd be glad if you set up the
repository on alioth.
> I also did a couple of changes myself:
> * Add ${misc:Depends} to all packages as recommended in debhelper >= 5 mode
> and add ${shlibs:Depends} to -dev packages which sneak extra deps if they
> start shipping binaries.
Have you some documentation pointers for this? In the 32bit multilib sections of
libz and libasound there are also some bidev / bilib dependencies. Do
you know where they come from? Maybe some Ubuntu magic?
Thanks to all,
Gregor
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
