I don't understand why this change is not merged yet. It is very useful when we push new tags into a git repo.

@Seldaek What's your opinion on this one?

Given the fact that webhooks from Github/Bitbucket only contain Git repository URLs and not Composer package names, this change would be very useful to trigger updates for single packages.

Why doesn't this use the merging of packages as the package filter does, see https://github.com/Tyrael/satis/blob/partial_update/src/Composer/Satis/Command/BuildCommand.php#L195 - is the cache file really needed?

#110 was created before the packages filter was added (originally with 4e9780a then later renamed) and I did not realize that new helper method when porting the original PR.

@Tyrael I realize the history, but would be nice to update this now then if possible?

sure, and I will update the PR, I was just answering your question why was this not done that way in the first place :)

@naderman any chance you had the time to review this?

while going through the comments from @stof I've just realized that @naderman suggestion in #232 (comment) was probably that we should instead extend selectPackages() and loadDumpedPackages() with a $repositoriesFilter similarly how it was done for $packagesFilter.
@naderman if that's what you wanted just let me now and I can do that.

How does it look? I could really use this, I have patched satis for now

It needs to be rebased unfortunately.

@Tyrael Can you please try to move this forward if you have time?

Or I can try it if you are busy.

originally I just forwardported the quick and dirty solution but then I realized/was suggested a better approach but then got swamped with work at my dayjob and couldn't finish it.
I'm not given up on this but I don't think I can work on it for like another 2-3 weeks.

Just for clarification...

I assume combining --repository-url and package in one command is reduntant (and currently breaks packages). Should they be handled as mutually exclusive?

Wouldn't it be better/easier to reuse package for repository URL as well and then based on argument type (repository URL, package name) get correct repository? Even though that might be a bit confusing as far as arguments go.

I looked at the latest code and it moved miles ahead...

After a bit of searching I found that this could be easily solved with just changing findPackages in Composer\Repository\ArrayRepository to include comparison of $package->getSourceurl("") (or create a separate method for that) and then it could be used together with package filter, e.g.

php bin\satis build satis.json public psr/log https://github.com/realshadow/serializers.git

Although I am not sure if it should go there. Any thoughts @alcohol, @Tyrael ?

@realshadow you mean you want to introduce changes to Composer for a feature in Satis? That is unlikely to happen unless you have a really good reason. Also I kind of lost track of what this PR was trying to accomplish since it's a port of a port (and I don't use Satis myself).

@alcohol Not really. Just saying :)

It was trying to accomplish building of a single/multiple repositories with repository url instead of package name. The original proposal was for --repository-url argument. @Tyrael then wanted to do like suggested in #232 (comment), but since then satis moved miles ahead and both mentioned methods do not exist anymore, instead the filtering is handled by composer itself via findPackages (thus my comment above).

Although on second thought, the original code, with slight alterations should be enough to cover this use case...

The code was mostly broken into smaller manageable pieces. It should still exist to some extend.

I have created a new PR #266 which uses PackageSelection for filtering.

I guess it can be closed ;)