Re: Merge repositories for CUPS Snap and CUPS OCI/Docker Container into the CUPS repo itself

Michael Sweet <[email protected]> Sat, 21 Dec 2024 18:33:52 -0500
Newsgroups dev.linux.lists.printing-architecture
Message-ID <[email protected]>
Till,

> On Dec 21, 2024, at 4:55 PM, Till Kamppeter <[email protected]> wrote:
> 
> On 12/21/24 22:06, Michael Sweet wrote:
> > We might as well.  However, you should probably also document how you'll manage the versioning since there are so many other components that get packaged with CUPS to make a working snap...  Doing MAJOR.MINOR.PATCH.BUILD versioning is probably sufficient for the snap versioning but it would be nice for users to be able to easily get a list of the bundled components and their versions as well.
> 
> The versioning is the same as distribution do when the package upstream software. They take the upstream release number and add an integer number separated by a dash, the package release number:
> 
> CUPS 2.4.12-1

I thought that snap used semantic version numbering?

WRT the rest of the stuff you wrote, let's make sure to add this as documentation ("SNAPCRAFT.md" or something similar at the top) so it is clear how CUPS is being packaged for snapcraft.

________________________
Michael Sweet