On Wed, Dec 15, 2021 at 11:42:21AM +, Stuart Henderson wrote:
> On 2021/12/15 01:03, Antoine Jacoutot wrote:
> > These error cases you are mentioning will happen in bulk as soon as
> > something depend on the compact subpackage
>
> Or the main package, if they're added there ;)
I see what y
On Wed, Dec 15, 2021 at 11:42:21AM +, Stuart Henderson wrote:
> On 2021/12/15 01:03, Antoine Jacoutot wrote:
> > These error cases you are mentioning will happen in bulk as soon as
> > something depend on the compact subpackage
>
> Or the main package, if they're added there ;)
Which is my
On 2021/12/15 01:03, Antoine Jacoutot wrote:
> These error cases you are mentioning will happen in bulk as soon as something
> depend on the compact subpackage
Or the main package, if they're added there ;)
These error cases you are mentioning will happen in bulk as soon as something
depend on the compact subpackage
—
Antoine
> On 15 Dec 2021, at 00:55, Klemens Nanni wrote:
>
> On Wed, Dec 15, 2021 at 12:49:39AM +0100, Antoine Jacoutot wrote:
>> Do we need to sub package? Can’t we include every
On Wed, Dec 15, 2021 at 12:49:39AM +0100, Antoine Jacoutot wrote:
> Do we need to sub package? Can’t we include everything in main?
I have no idea if ports suddenly pick up the new headers and/or whether
there are any other side effects.
Subpackages seemed cleaner and explicit; they avoid these
Do we need to sub package? Can’t we include everything in main?
Anyway the change from libv4l to libv4l,-main is not needed as it’s the
default.
—
Antoine
> On 14 Dec 2021, at 13:50, Klemens Nanni wrote:
>
> Video4Linux headers are required for an ongoing porting effort;
> FreeBSD has a ded
Video4Linux headers are required for an ongoing porting effort;
FreeBSD has a dedicated port for this that reaches back to their libv4l
port it seems, which looks practically identical to our MULTI_PACKAGES.
I just package the headers that are needed in their own subpackage.
The actual libv4l pack
