Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 877639 - dev-php/composer-2.4.3 version bump
Summary: dev-php/composer-2.4.3 version bump
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Guillaume Seren
URL: https://github.com/composer/composer/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-19 10:29 UTC by r7l
Modified: 2024-02-29 09:08 UTC (History)
10 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description r7l 2022-10-19 10:29:14 UTC
Current Composer is outdated. Any chance of getting the latest version into Portage? Thanks allot.

Reproducible: Always
Comment 2 Ferdinand Kuhl 2023-02-19 22:25:35 UTC
I have created a repository with all ebuilds needed for a current composer:

https://github.com/digital-competence/composer-ebuilds

Maybe this helps to get it into portage? Should I create a PR against the public repo? As there are soooo many packages I did not dare. And I even do not know, if the packages match the quality standards.

But at least composer is working. ;)
Comment 3 r7l 2023-02-20 10:45:48 UTC
Thanks allot! I've also started looking into this but didn't finish it yet. Writing PHP Ebuilds is rather complicated compared to the rest. At least when comparing to the existing Ebuilds.

I'll get it in touch with you on Github to not pollute in here.
Comment 4 Joonas Niilola gentoo-dev 2023-02-28 18:07:45 UTC
(In reply to Ferdinand Kuhl from comment #2)
> I have created a repository with all ebuilds needed for a current composer:
> 
> https://github.com/digital-competence/composer-ebuilds
> 
> Maybe this helps to get it into portage? Should I create a PR against the
> public repo? As there are soooo many packages I did not dare. And I even do
> not know, if the packages match the quality standards.
> 
> But at least composer is working. ;)

It'd be great! Your contribution will be reviewed and brought up to minimal quality standards before merged, so if you're just willing to work for that, everything should be fine.
Comment 5 Rahil Bhimjiani 2023-08-22 14:44:08 UTC
I see that r7l & Ferdinand Kuhl are maintaing https://github.com/gentoo-php-overlay/php-overlay 

Have either of you created a PR? 

If nobody is maintaining dev-php/composer::gentoo then rather should be removed from official repo.
Comment 6 Rahil Bhimjiani 2023-10-06 15:24:38 UTC
Version 2.6.5 released. 
https://github.com/composer/composer/releases

Can someone at least add maintainer-needed?
Comment 7 r7l 2023-10-12 09:51:47 UTC
@Rahil Bhimjiani I've not created a PR just yet. But the latest version of Composer should be in our overlay by now.

My main issue with PRs is the additional work regarding tests within the Ebuilds. The ones we have on the overlay aren't having anything regarding tests and when i was looking into it once, it seemed as if it would double the amount of dependencies.

If i find some time, i might start working on PR.
Comment 8 Rahil Bhimjiani 2023-10-12 10:07:09 UTC
You dont HAVE TO add tests. Just add RESTRICT=test and it'll be fine. As long ebuild compiles as upstream intended with relevant docs, PR is enough. 

Would rather have ebuild with broken/null tests than have ancient unmaintained version in ::gentoo
Comment 9 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-10-12 10:10:57 UTC
(In reply to Rahil Bhimjiani from comment #8)
> You dont HAVE TO add tests. Just add RESTRICT=test and it'll be fine. As
> long ebuild compiles as upstream intended with relevant docs, PR is enough. 
> 
> Would rather have ebuild with broken/null tests than have ancient
> unmaintained version in ::gentoo

Well, that's not quite right. We strongly prefer tests and it's the only real way to make sure something works. And yes, sometimes one has to do more work to get there - that's the cost of doing things properly.

But it's okay to restrict tests if you're slowly working on adding the relevant test dependencies or something.
Comment 10 Sam Resto 2024-02-20 23:39:29 UTC
So, basically, what we're waiting for is a PR with dev-php/composer and related dependencies up to date. From the sounds of it, testing is desired but not required, correct? Especially since there is no ebuilds for phpunit anymore.
Comment 11 Sam Resto 2024-02-28 03:58:23 UTC
In a nutshell, I got this to build with current latest packages as-of 2/27/2024.

Currently without tests, as that would require pulling in phpunit which is also nonexistent in the repos and looks like... a bit of effort at this time to just get this going. I'll work on it some more, but please lets not delay this too much at this point.

At GitHub: https://github.com/user00265/composer-overlay
Comment 12 Sam Resto 2024-02-28 04:54:53 UTC
(In reply to Sam Resto from comment #11)
> In a nutshell, I got this to build with current latest packages as-of
> 2/27/2024.
> 
> Currently without tests, as that would require pulling in phpunit which is
> also nonexistent in the repos and looks like... a bit of effort at this time
> to just get this going. I'll work on it some more, but please lets not delay
> this too much at this point.
> 
> At GitHub: https://github.com/user00265/composer-overlay

I forgot to mention, WIP. It installs, but the autoloader from composer not being used and being stripped for the Fedora autoloader is... well, not ideal for my head. Can't quite wrap my brain around it yet.