Skip to contentSkip to conversation

v4l-utils 1.24.0 has been released

DISCUSSION Gregor Jasny 4 participants 6 messages Feb 23, 2023 – May 4, 2023 Media (V4L/DVB)

lore
Share & tools
lore
#1 lore raw

v4l-utils 1.24.1 has been released

Hello,

the first patch release of v4l-utils has been release as 1.24.1.

Changes:

Quoted 2 lines

Hans Verkuil (1):
v4l2-tracer: use __s64 instead of long

Thanks,
Gregor

#2 lore raw
In reply to Gregor Jasny

Hi Gregor,

Em Thu, 23 Feb 2023 10:44:41 +0100
Gregor Jasny <[email protected]> escreveu:

Quoted 9 lines

Hello,

I'm happy to announce that v4l-utils 1.24.0 has been released. This will be the last version before the build system will be migrated from Autotools to Meson.

Changelog:
https://git.linuxtv.org/v4l-utils.git/tree/ChangeLog?h=v4l-utils-1.24.0
Download: https://linuxtv.org/downloads/v4l-utils/v4l-utils-1.24.0.tar.bz2

I wouldn't mind if we would have a shorter release time for version 1.26 - or maybe it is time to increase major, so version 2.0.

As we are now using a new building system, it would be nice to have a stable version frozen, with not much other changes, in order to allow distros to opt either to use version 1.24 with autotools or to migrate to the newest version, with meson, but not many other changes.

So, perhaps we should aim release a new version in 2 months or so, once we have enough time to do cleanups if needed and having media maintainers and developers familiar with the new way.

Comments?

PS.: on that matter, I took ahead and changed Fedora rawhide v4l2-utils package to use the new building system:

	https://bodhi.fedoraproject.org/updates/FEDORA-2023-43964d4d83

That helped to identify a bug after the migration at the man page location, and hopefully would help to have more tests on a more realistic scenario (e. g. after packaged on distributions).

Thanks,
Mauro

#3 lore raw

Hello Mauro and list

Quoted 15 lines · Mauro Carvalho Chehab

Gregor Jasny <[email protected]> escreveu:

Quoted 4 lines

I'm happy to announce that v4l-utils 1.24.0 has been released. This will be the last version before the build system will be migrated from Autotools to Meson.

I wouldn't mind if we would have a shorter release time for version 1.26 - or maybe it is time to increase major, so version 2.0.

As we are now using a new building system, it would be nice to have a stable version frozen, with not much other changes, in order to allow distros to opt either to use version 1.24 with autotools or to migrate to the newest version, with meson, but not many other changes.

Quoted 3 lines

So, perhaps we should aim release a new version in 2 months or so, once we have enough time to do cleanups if needed and having media maintainers and developers familiar with the new way.

It looks like the dust after the meson migration has been settled. When would be a good time for a new v4l-utils release? I'm available this weekend or the upcoming ones.

Is there anything you'd like to land in the mainline branch prior to a new release?

Thanks,
Gregor

#4 lore raw

Hi Gregor and list,

Quoted 18 lines · Gregor Jasny

Hello Mauro and list

Quoted 15 lines · Mauro Carvalho Chehab

Gregor Jasny <[email protected]> escreveu:

Quoted 4 lines

I'm happy to announce that v4l-utils 1.24.0 has been released. This will be the last version before the build system will be migrated from Autotools to Meson.

I wouldn't mind if we would have a shorter release time for version 1.26 - or maybe it is time to increase major, so version 2.0.

As we are now using a new building system, it would be nice to have a stable version frozen, with not much other changes, in order to allow distros to opt either to use version 1.24 with autotools or to migrate to the newest version, with meson, but not many other changes.

Quoted 7 lines
Quoted 3 lines

So, perhaps we should aim release a new version in 2 months or so, once we have enough time to do cleanups if needed and having media maintainers and developers familiar with the new way.

It looks like the dust after the meson migration has been settled. When would be a good time for a new v4l-utils release? I'm available this weekend or the upcoming ones.

Is there anything you'd like to land in the mainline branch prior to a new release?

Actually, there is one thing I want to discuss. I maintain the edid-decode utility
(https://git.linuxtv.org/edid-decode.git/) and I have received several request for 'a proper version number' and releasing it as a package.

I have been wondering whether this utility shouldn't be moved to v4l-utils so it is part of the v4l-utils release mechanism.

Since V4L2 also deals with setting/getting EDIDs it is not unreasonable.

Would there be any objections if I did that? If there are no objections, then it would be nice to include this in a new release.

Regards,

Hans

#5 lore raw

Hi Hans,

Quoted 31 lines · Hans Verkuil
Quoted 19 lines · Gregor Jasny
Quoted 14 lines · Mauro Carvalho Chehab

Gregor Jasny <[email protected]> escreveu:

Quoted 3 lines

I'm happy to announce that v4l-utils 1.24.0 has been released. This will be the last version before the build system will be migrated from Autotools to Meson.

I wouldn't mind if we would have a shorter release time for version 1.26 - or maybe it is time to increase major, so version 2.0.

As we are now using a new building system, it would be nice to have a stable version frozen, with not much other changes, in order to allow distros to opt either to use version 1.24 with autotools or to migrate to the newest version, with meson, but not many other changes.

Quoted 3 lines

So, perhaps we should aim release a new version in 2 months or so, once we have enough time to do cleanups if needed and having media maintainers and developers familiar with the new way.

Quoted 6 lines

It looks like the dust after the meson migration has been settled. When would be a good time for a new v4l-utils release? I'm available this weekend or the upcoming ones.

Is there anything you'd like to land in the mainline branch prior to a new release?

Actually, there is one thing I want to discuss. I maintain the edid-decode utility
(https://git.linuxtv.org/edid-decode.git/) and I have received several request for 'a proper version number' and releasing it as a package.

Quoted 7 lines

I have been wondering whether this utility shouldn't be moved to v4l-utils so it is part of the v4l-utils release mechanism.

Since V4L2 also deals with setting/getting EDIDs it is not unreasonable.

Would there be any objections if I did that? If there are no objections, then it would be nice to include this in a new release.

No objection from me. It could be nice at some point to work on v4l-utils packaging to make it easier to split key utilities in different packages, but there's no urgency.

Signature · 3 lines
Regards,

Laurent Pinchart