From: Till Kamppeter <till.kamppeter@gmail.com>
To: Rudra Pratap Singh <rudransh.iitm@gmail.com>,
Michael Sweet <msweet@msweet.org>
Cc: OpenPrinting <printing-architecture@lists.linux.dev>,
Cristovao Cordeiro <cristovao.cordeiro@canonical.com>,
Soumyadeep Ghosh <soumyadeepghosh2004@zohomail.in>
Subject: Re: Merge repositories for CUPS Snap and CUPS OCI/Docker Container into the CUPS repo itself
Date: Sun, 22 Dec 2024 16:33:01 +0100 [thread overview]
Message-ID: <34cc8c02-8e8a-47ba-856f-9ce834bd4496@gmail.com> (raw)
In-Reply-To: <CADmOQafms3c=7FAzeX9cbvnPOYDcf9Xxe9QyKUjYEYTgJq3AJw@mail.gmail.com>
On 12/22/24 16:26, Rudra Pratap Singh wrote:
> To clarify, the feature to update the README.md file is not currently available
> in the desktop-snaps action. To implement this, I would need to dive into their
> codebase (which I am already familiar with) and make modifications to suit our
> specific requirements.
>
> Whether this concerns the repository's main |README.md| file or a separate one
> for the packaged CUPS, I will ensure it is tailored appropriately.
>
> Best regards,
> Rudra
You could make an entry (a comment) in snapcraft.yaml and rockcraft.yaml which
is/are the files to create the component version list in or just search files in
the base directory of the repo and in the directory where the *craft.yaml is in
whether they have the appropriate "## Included Components" mark and then
auto-update these files.
Till
next prev parent reply other threads:[~2024-12-22 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 23:55 Merge repositories for CUPS Snap and CUPS OCI/Docker Container into the CUPS repo itself Till Kamppeter
2024-12-21 21:06 ` 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 [this message]
[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=34cc8c02-8e8a-47ba-856f-9ce834bd4496@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 \
--cc=soumyadeepghosh2004@zohomail.in \
/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.