Date: Wed, 1 Mar 2017 20:05:45 +0300 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: Mathieu Arnold <mat@FreeBSD.org> Cc: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r435017 - head/devel/p5-Contextual-Return Message-ID: <20170301170545.GA27031@hades.panopticon> In-Reply-To: <f19d2ca3-0c44-b51c-971a-ce640fc6cfdf@FreeBSD.org> References: <201702280945.v1S9jF0K067267@repo.freebsd.org> <20170228152911.GA85667@hades.panopticon> <f19d2ca3-0c44-b51c-971a-ce640fc6cfdf@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Mathieu Arnold (mat@FreeBSD.org) wrote: > >> Date: Tue Feb 28 09:45:15 2017 > >> New Revision: 435017 > >> URL: https://svnweb.freebsd.org/changeset/ports/435017 > >> > >> Log: > >> Update to 0.004010 > >> > >> - Use real PORTVERSION > > Thank you for these! > > I am not sure these version changes are a good idea. > Perl versions do not behave the same as Port versions, in some very > radical ways, for example, in Perl land, 1.1 > 1.1.1 (because 1.1.1 > really means 1.001001) > All the ports that have been converted to use the real version numbers > will see their PORTEPOCH bumped a lot as number go ahead. I don't see any problems with using PORTEPOCH. Using fake versions brings a lot of confusion though. Manual intervention will still be required for portscout and repology (e.g. ignoring older versions which compare higher than newer ones), but at least version will be comparable and correspond to upstream. I also had a feeling that perl module authors seem to stick to sane versioning scheme after 2010. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://amdmi3.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170301170545.GA27031>