Changes between Initial Version and Version 1 of Ticket #54125, comment 2
- Timestamp:
- May 7, 2017, 2:47:01 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #54125, comment 2
initial v1 1 Changing the advertised would mean adapting the distname calculation as well as the livecheck. Not a big deal, but why bother using a different version, or a different version rewritten this way? Why not `19.6.0.2016.10.30` while we're at it, for instance? 1 Changing the advertised would mean adapting the distname calculation as well as the livecheck. Not a big deal, but why bother using a different version, or a different version rewritten this way? Why not `19.6.0.2016.10.30` while we're at it, for instance? Upstream must have had a reason to pick the version string they did and it's not like MacPorts needs standardised version numbers for us in depspecs or the like ;) 2 2 3 3 The 2 make calls in the `tools` variant are to ensure that the respective targets are built. They're not run by the current build system, so there's no interference with `port test`. You're right that I could add the targets via `build.target-append`.