From: Till Kamppeter <till.kamppeter@gmail.com>
To: OpenPrinting <printing-architecture@lists.linux.dev>,
Michael Sweet <msweet@msweet.org>,
rudransh.iitm@gmail.com
Cc: Cristovao Cordeiro <cristovao.cordeiro@canonical.com>
Subject: Merge repositories for CUPS Snap and CUPS OCI/Docker Container into the CUPS repo itself
Date: Sat, 21 Dec 2024 00:55:50 +0100 [thread overview]
Message-ID: <1ca4c555-aa30-43db-a9b4-74bd2729f8dc@gmail.com> (raw)
Hi,
when I started snapping CUPS back in 2017, the CUPS source was still maintained
at Apple and therefore I created the separate repo cups-snap at OpenPrinting.
As I generally recommend that Snaps should be created by the respective upstream
projects I am snapping all the projects of OpenPrinting, including CUPS, and
also the (retro-fitting) Printer Applications and ipp-usb. As for the Printer
Applications and ipp-usb the repositories were all the time at OpenPrinting I
have included the files for snapping them right into their repositories. The
same I did now also with the files to create the rockcraft-based OCI container
images, on which Rudra (CCed) has worked in his GSoC project, with Cristovão
(also CCed) as mentor.
Now we arrived also at the point what to do with CUPS, and my suggestion is to
not only add the OCI-container-related files to the CUPS 2.x repository "cups"
but then also migrate "cups-snap" to "cups", so that all the
distribution-independent packaging methods are included in the "cups"
repository, where also the code is.
For CUPS 3.x we can then migrate the two packaging methods Snap and OCI
container over to the two new CUPS daemons, "cups-local" and "cups-sharing", so
that each of them will be available in the Snap Store but also on OCI container
image "stores" like DockerHub.
This is Rudra's final report of his GSoC project:
https://medium.com/@rudransh.iitm/gsoc-2024-final-report-container-chronicles-759fe7f23ac6
This is Rudra's repository of the CUPS container image:
https://github.com/rudra-iitm/cups-rock
Rudra's work on the retro-fitting Printer Applications is already in the
appropriate repositories "ps-printer-app", "ghostscript-printer-app",
"hplip-printer-app", "gutenprint-printer-app".
Mike, WDYT? Should we migrate the Snap and OCI-image repos into the CUPS one?
Till
next reply other threads:[~2024-12-20 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 23:55 Till Kamppeter [this message]
2024-12-21 21:06 ` Merge repositories for CUPS Snap and CUPS OCI/Docker Container into the CUPS repo itself Michael Sweet
2024-12-21 21:55 ` Till Kamppeter
2024-12-21 23:33 ` Michael Sweet
[not found] ` <CADmOQacnfVS5VR+dpudVt2NxgV_HG+K0in0mm-h5Hwe0nfF0cQ@mail.gmail.com>
2024-12-22 13:43 ` Michael Sweet
2024-12-22 14:03 ` Till Kamppeter
2024-12-22 14:44 ` Michael Sweet
2024-12-22 15:28 ` Till Kamppeter
[not found] ` <CADmOQafms3c=7FAzeX9cbvnPOYDcf9Xxe9QyKUjYEYTgJq3AJw@mail.gmail.com>
2024-12-22 15:33 ` Till Kamppeter
[not found] ` <CADmOQadkw-BY2vNqQtJDqi7TqGpHErVM29rkPfGAajiFVhGUiw@mail.gmail.com>
2024-12-22 15:40 ` Till Kamppeter
[not found] ` <CADmOQae0YNffRYsMZLLcwMY2GxFpThyfaq5Hm0rw=ke0pkuvZw@mail.gmail.com>
[not found] ` <CADmOQaf4hsBwrz-qkW_o8SZnfP1faD9ma4+T1FyA_GUYRgKhuQ@mail.gmail.com>
2025-01-13 17:55 ` Michael Sweet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ca4c555-aa30-43db-a9b4-74bd2729f8dc@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=cristovao.cordeiro@canonical.com \
--cc=msweet@msweet.org \
--cc=printing-architecture@lists.linux.dev \
--cc=rudransh.iitm@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.