Perl 6 - the future is here, just unevenly distributed

IRC log for #native, 2016-01-13

| Channels | #native index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
04:41 plicease salva++ for all the good PRs for AB lately.
07:23 salva plicease: thanks, I am just scratching my itches!
07:24 salva BTW, I have another issue to report :-)
07:24 salva when releasing development versions, you go from 0.24 to 0.24_01
07:25 salva and it seems that cpanm (at least) thinks that 0.24 > 0.24_01
07:26 salva so it is not possible to specify a dependency on 0.24_01 on a Build.PL script
07:26 salva cpanm will actually download 0.24 instead
07:27 salva My recommendation would be to use completely different numbers for stable and development releases in order to avoid this confusion
07:27 salva For instance, from 0.25 go to 0.26_01, 0.26_02, etc, and then release as stable 0.27
07:29 salva even if the issue is fixed in cpanm, it would still be clearer for humans to understand which one is the later version
11:22 nicomen I thought underscore versions meant development releases, and should not automatically be used
11:24 nicomen actually cpan should not even index it for download
11:42 salva cpan doesn't install dev versions by default
11:44 salva but if they are requested explicitly in Build.PL or Makefile.PL and no later stable version is available the development version is used
11:44 salva or if you just request it explicitly as in "cpanm Alien::Base~0.24_01"
11:46 salva In my particular case, I need the latest dev Alien::Base for Alien::Libssh2
12:37 plicease I'm not sure that it is a good idea to specify a dev version in Build/Makefile.PL anyway
12:37 plicease the intent is to get feedback from cpantesters
12:38 plicease and for devs to try out new features but they have to explicitly install it themsevles
12:41 plicease The dev versions have not been tested as much as may have bugs, or features that will be removed before the prod release
12:41 plicease for AB the latter hasn't happened yet, but the former definitely has
13:02 salva plicease: In my case I have a development version of a module that depends on a development version of Alien::Base
13:03 salva and I am using Travis CI to test it
13:03 salva Travis CI uses cpanm
13:04 salva so it fails to handle the dependency automatically for me.
13:09 plicease that is admittedly annoying.  In the past I have explicitly installed dev versions from the .travis.yml
13:09 plicease or for AB you can install it directly from github
13:10 plicease EUMM seems to use the version policy that you describe.
13:10 plicease its dev cycle seems to be a lot longer than for AB though.
13:52 salva yes, i can do a "cpanm Alien::Base@0.24_01" that installs exactly that version
13:52 salva but then I have to change it again when a new version comes out
14:08 plicease what about: cpanm --dev Alien::Base
14:08 plicease you need a recent cpanm, not sure if the travis version is up to it.

| Channels | #native index | Today | | Search | Google Search | Plain-Text | summary