Comments (5)
Please discuss it on composer. Packagist is not responsible for parsing versions
from packagist.
You can just "require": {"symfony/framework-bundle": "2.0.*"}
. That indicates just fine that the bundle is made for 2.0. Even better it will enforce it. Sorry but I don't think version strings should have that kind of information mingled in them.
from packagist.
@Seldaek Sorry but I'm lost with this. So if I have a version for SF 2.0 and
other for SF 2.1 then both versions can share exactly the same version
number Ex: v1.0.0
That will produce an nondeterminist situation when someone will add the
package into his composer
require": {"vendor/test-bundle": "v1.0.0"}
What version will retrieve, the
version for SF 2.0 or the version for SF 2.1?
Maybe the correct way for naming will be v1.0.0 for SF2.0 and v2.0.0 for
SF2.1
I found this guidelines for PEAR packages
http://pear.php.net/group/docs/20040226-vn.php This are correct for packagist?
from packagist.
@Maks3w They cannot share the same version number if the code is different.
from packagist.
@Maks3w The point is, you should have a version of your bundle for Symfony2.0, that requires 2.0., and if it supports 2.1. as well you can require >=2.0,<2.2
. If your bundle at some point has to break compatibility, then you should do a new major release of your bundle, that only supports 2.1.*
. And you should have a 1.0
branch of your bundle to still provide patches to the 2.0.* version.
from packagist.
Related Issues (20)
- extend GitLab support HOT 2
- Installation stats graph visibility
- Respect 'dev' keyword in packagist UI to show composer require --dev HOT 1
- [FEATURE] Geographical installation chart HOT 1
- Resolve historic tags HOT 5
- Not receiving email when resetting password HOT 1
- Email users on account security changes to alert them to potential compromise
- Migrating to Bootstrap 5.3 HOT 1
- Can get the user details HOT 1
- Fix typo on API documentation page
- SSH source URLs being used for github.com HOT 2
- Allow proposed PIE extensions to be submitted to Packagist HOT 6
- Invalid package information: funding.1.url HOT 5
- Show homepage from default branch HOT 3
- Dropdown menu no longer works HOT 3
- Syntax Highlighting in README.md seems not to work properly when coming from Bitbucket HOT 4
- Readme is not shown to guests HOT 1
- require-dev dependencies to packages overwritten in composer.json shouldn't be links HOT 1
- Allow prefixes when parsing SemVer HOT 1
- not detecting subfolder in github repo HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from packagist.