-
Notifications
You must be signed in to change notification settings - Fork 34
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
Release as a Composer package #5
Conversation
Will do Jukka! Thanks! |
👍 Please merge this |
👍 |
Another 👍 - this would be great in composer! |
@tubalmartin looks good, but i wouldn't take that semver stuff too seriously, it's recommendation not requirement. if you have you own versioning schema, that's fine. i just hope the semver is the reason why you haven't merged this yet. |
Release as a Composer package
please register the package in packagist.org as well (step 2), otherwise it does not work |
It's on packagist already. |
ok, but no tags. can you push at least some tags out? i think their web interface had something. https://packagist.org/packages/tubalmartin/cssmin as i tried |
Tag v2.4.8-p4 pushed. "p" stands for "patch". :) |
so, it did not liked your |
Yeah, it wasn't semver compliant. Adding a letter after the dash makes it Túbal Martín 2014-09-22 10:45 GMT+02:00 Elan Ruusamäe notifications@github.com:
|
Hi, first of all, thank you for creating this PHP port of YUI CSS compressor. It has come handy.
Getting this thing on Composer would be awesome. This library is one of the few last libraries, that I use, that aren't available though composer.
Composer might seem pretty confusing if you aren't already familiar with it, but fear not; getting a Composer package out there isn't hard. At minimum it only requires the JSON meta file (as in the PR). Adding the meta file is the minimum, but to get most out of Composer, the library should also be registered on the central repository, Packagist. Registering the package makes consuming it easier, as you can refer to it by its short name (see the slightly altered README.md in the PR).
To make version contraints resolvable, the repository should use semantic versioning, which is what Composer uses. Otherwise users can not define contraints; Users can fetch the library, but only by referencing a commit, a tag, a branch or by a wildcard.
In short, this all comes down to few simple steps;
Regards,
Jukka