Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import packages from git/svn/.. #2

Closed
Seldaek opened this issue Jun 9, 2011 · 6 comments
Closed

Import packages from git/svn/.. #2

Seldaek opened this issue Jun 9, 2011 · 6 comments
Assignees

Comments

@Seldaek
Copy link
Member

Seldaek commented Jun 9, 2011

The current form to add packages and specify everything was good for testing, and it still will be useful to add packages that don't have a composer.json file, but we need automatic import from git repos and such.

Whoever does that can use https://github.com/Seldaek/monolog/ as an example. It contains a valid composer.json file.

@ghost ghost assigned Seldaek Jun 29, 2011
@xaav
Copy link
Contributor

xaav commented Jun 30, 2011

Should this be done on a cron? (I'm assuming yes)

@stof
Copy link
Contributor

stof commented Jun 30, 2011

@xaav I don't think Packagist need to discover the repos itself currently (it would be tied to site which provide a search functionnality allowing to know whether there is a composer.json file, and I don't think this exists). But the idea would be to provide the url of the repo and let Packagist retrieve the data from the composer.json file instead of asking the maintainer to give them.

@Seldaek
Copy link
Member Author

Seldaek commented Jun 30, 2011

It's done with a cron, and I'm working on this so don't waste time :)

@Seldaek
Copy link
Member Author

Seldaek commented Jul 6, 2011

Just pushed the github importer. It doesn't support non-github repos yet, or any other VCS, and it needs to be cleaned up like hell before it can be extended.

@xaav
Copy link
Contributor

xaav commented Aug 4, 2011

Since the basic framework for this is there, you should close this issue, and open a separate issue for each additional VCS you want to support.

@Seldaek
Copy link
Member Author

Seldaek commented Aug 4, 2011

You're right it's in a decent shape now I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants