CMSP 23. Have a "development version" flag
23. Have a "development version" flag Proposal: Add a boolean value indicating whether the release is a "production" or "alpha/developer/beta/whatever" release. [[User:elliot|Elliot Shank]] Comments: *...
View ArticleCMSP 23. Have a "development version" flag
* David Golden [2009-10-09T07:52:45] Packlist 2.0? -- rjbs -- Ricardo Signes
View ArticleCMSP 23. Have a "development version" flag
Agreed. The main use of development status seems to be control if the distribution is indexed as the latest released etc. So having a flag instead of the hackish way we use _ seems a benefit. Graham....
View ArticleCMSP 23. Have a "development version" flag
-1 for this reason. Reinventing packlists and EU::Install* while retaining backward compatibility seems like a big can of worms that may grind this effort to a halt. Steffen -- Steffen Mueller
View ArticleCMSP 23. Have a "development version" flag
Correction to my earlier reply: If we have the META info available *easily* post installation (cf. 33), my vote becomes a +1. Steffen -- Steffen Mueller
View ArticleCMSP 23. Have a "development version" flag
That's the idea, which is why I'm in favor. Compared to a release_status field, this would be purely binary and thus not subject to people inventing new status categories. -- David -- David Golden
View ArticleCMSP 23. Have a "development version" flag
-=| Graham Barr, Fri, Oct 09, 2009 at 09:20:37AM -0500 |=- +1 Getting rid of _ will simplify downstream handling of versions. Currently one has to dig into CHANGES in order to determine if 1.002_04 is...
View Article
