Bug#488117: Preliminary libv4l packages?

2008-07-09 Thread Domenico Andreoli
On Wed, Jul 09, 2008 at 03:20:20PM +0200, Julien BLACHE wrote: > Hi Domenico, Hi, > Do you have preliminary packages for libv4l already? If yes, can you > put them up somewhere? I'd like to grab them to try out libv4l for > SANE. Unfortunately I have not. While I am very interested in this libra

Bug#488117: Preliminary libv4l packages?

2008-07-09 Thread Julien BLACHE
Domenico Andreoli <[EMAIL PROTECTED]> wrote: Hi, > Romain offered collaboration to the job, I hope he still can take over > the effort to package it. He has the right to (not) add me as uploader, > for the near future I am going to be rather passive. Sorry. Romain, what are your plans? Thanks f

Bug#488117: Preliminary libv4l packages?

2008-07-09 Thread Romain Beauxis
Le Wednesday 09 July 2008 19:13:50 Julien BLACHE, vous avez écrit : > Hi, Hi all ! > > Romain offered collaboration to the job, I hope he still can take over > > the effort to package it. He has the right to (not) add me as uploader, > > for the near future I am going to be rather passive

Bug#488117: Preliminary libv4l packages?

2008-07-09 Thread Julien BLACHE
Romain Beauxis <[EMAIL PROTECTED]> wrote: Hi, > In particular, the library is included in v4l-dvb tree, so it perhaps should > be packaged from something bigger taken from there... Given that it is not tightly coupled with v4l-dvb, I do not see what you'd gain by coupling the library to somethi

Bug#488117: Preliminary libv4l packages?

2008-07-09 Thread Domenico Andreoli
On Wed, Jul 09, 2008 at 09:10:07PM +0200, Julien BLACHE wrote: > Romain Beauxis <[EMAIL PROTECTED]> wrote: > > > In particular, the library is included in v4l-dvb tree, so it perhaps > > should > > be packaged from something bigger taken from there... > > Given that it is not tightly coupled wi

Bug#488117: Preliminary libv4l packages

2008-07-27 Thread Gregor Jasny
Hi, today I've started to package libv4l. Open issues: * Would it make sense to split the package into 3 libs, 3 -dev and maybe 2 preload libs? To me it seems to be pure overkill. Policy §8.1 seems to allow stuffing all libs into one package * not sure if copyright file is correct * test with

Bug#488117: Preliminary libv4l packages

2008-08-01 Thread Domenico Andreoli
On Sun, Jul 27, 2008 at 12:54:51PM +0200, Gregor Jasny wrote: > Hi, Hi :) > today I've started to package libv4l. Open issues: > * Would it make sense to split the package into 3 libs, 3 -dev and maybe > 2 preload libs? To me it seems to be pure overkill. Policy §8.1 seems to > allow stuffin

Bug#488117: Preliminary libv4l packages

2008-08-01 Thread Gregor Jasny
Hi, I've packaged the new v0.3.9. Improvements over v0.3.7: * Build static libs (patch sent upstream) * Install pkgconfig files * Use quilt for patch management Still missing/unchecked: * copyright file * shlibs stuff Cheers, Gregor libv4l_0.3.9-1.diff.gz Description: application/gzip -BE

Bug#488117: Preliminary libv4l packages

2008-08-02 Thread Gregor Jasny
* fixed pkginfo files for static linking * add 32 bit compatibility libs for preloading to Skype libv4l_0.3.9-2.diff.gz Description: application/gzip -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.0 Source: libv4l Binary: libv4l, libv4l-dev, lib32v4l, lib32v4l-dev Architecture: any Ver