Hi,
On 2024/09/13 12:22, Michael Orlitzky wrote:
On 2024-09-11 17:23:16, Jaco Kroon wrote:
1. Let users (myself included) just download and use that.
2. We package the phar file rather than the individual deps. Yes, this
is cheating. Like using embedded libs, however, I've seen and observed
On 2024-09-11 17:23:16, Jaco Kroon wrote:
> 1. Let users (myself included) just download and use that.
> 2. We package the phar file rather than the individual deps. Yes, this
> is cheating. Like using embedded libs, however, I've seen and observed
> that in some cases this makes more sense th
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 vulnerab
Hi Michael,
Looks like we keep bumping into each other ... and not only on PHP packages.
n 2024/09/11 13:26, Michael Orlitzky wrote:
On Wed, 2024-09-11 at 09:33 +0200, Jaco Kroon wrote:
Hi,
I missed this announcement, looking specifically for composer again.
If I make the effort of bumping t
On Wed, 2024-09-11 at 09:33 +0200, Jaco Kroon wrote:
> Hi,
>
> 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'd re-commit if you're interested in keeping up wit
Hi,
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 htt
