> I'm not really happy with having to use patch > number as a publish-retry number.
This is conflating two problems though... using mutability to work around a stability problem for the sake of tidyness. While it'd be untidy for (during a period of instability) the patch number to be used as a proxy for the number of publish-retries, it's nowhere near as untidy as having your code change silently without any warning. When the stability issue is fixed the mutability would still be there to give me headaches. I appreciate that there are some workarounds, but having to check in all dependencies is also untidy. As is add an extra maintenance step that checksums dependencies and aborts if they have. I was hoping to either be educated to the reason for npm's package mutability, or to find consensus around changing it... I don't feel like I'v got either of those yet... Anybody? On Saturday, December 21, 2013, Alex Kocharin wrote: > > 20.12.2013, 00:13, "Sam Roberts" <[email protected] <javascript:;>>: > > On Wed, Dec 18, 2013 at 5:42 PM, Alex Kocharin > > <[email protected]<javascript:;>> > wrote: > > > >> So if something needs to be republished, maintainer will be > >> forced to change version number (or add a build number although it's > now > >> ignored by npm). > > > > I've found force republish invaluable in the last weeks when publishes > > to npmjs.org silently half-work, leaving the tarball missing from > > cloudfare. I'd prefer a build number, but like you say, its not > > respected by npm, and I'm not really happy with having to use patch > > number as a publish-retry number. > > What about using fourth number for it? Like "1.2.3-4"? If you document out > what this versioning means, it'll be fine since immutability is much more > valuable here than strict adherence to semver (which is proven to be a bad > default anyway). > > -- > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected]<javascript:;> > To unsubscribe from this group, send email to > [email protected] <javascript:;> > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:;>. > For more options, visit https://groups.google.com/groups/opt_out. > -- Richard Marr -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
