From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Last rites EAPI=6 packages: dev-php/*
Date: Fri, 13 Sep 2024 01:46:08 -0000 (UTC) [thread overview]
Message-ID: <pan$ac5e5$8c117d0d$c9be7fcc$3dee0eb@cox.net> (raw)
In-Reply-To: 5babde00-594b-42d6-aeec-9c2398e30a7f@uls.co.za
Jaco Kroon posted on Wed, 11 Sep 2024 09:33:10 +0200 as excerpted:
> I missed this announcement, looking specifically for composer again.
>
> If I make the effort of bumping to newest version, is this something
> that would be re-added to the tree?
>
> I note there were active security vulnerabilities under very specific
> conditions (composer.phar is exposed via http).
>
> Or should I rather just deploy this into a local overlay?
[Tree or local overlay?]
You seem to have missed the obvious middle option, deploying to a public
overlay.
If there's many related packages (another reply mentioned a bunch of deps;
not being a PHP person I wouldn't know...) that might most appropriately
be a dedicated overlay.
For single packages, particularly if there's likely to be others
interested, the guru overlay seems to be quite popular as a middle ground,
allowing multiple people to help without the full bureaucracy of the main
tree.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2024-09-13 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 17:20 [gentoo-dev] Last rites EAPI=6 packages: dev-php/* Arthur Zamarin
2024-09-11 7:33 ` [gentoo-dev] " Jaco Kroon
2024-09-11 11:26 ` Michael Orlitzky
2024-09-11 15:23 ` Jaco Kroon
2024-09-13 10:22 ` Michael Orlitzky
2024-09-13 11:53 ` Jaco Kroon
2024-09-13 1:46 ` Duncan [this message]
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='pan$ac5e5$8c117d0d$c9be7fcc$3dee0eb@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox