[MacPorts] #55286: gr-lora: Don't change the version in a variant

MacPorts noreply at macports.org
Fri Nov 10 10:07:33 UTC 2017


#55286: gr-lora: Don't change the version in a variant
------------------------+-----------------------
 Reporter:  ryandesign  |      Owner:  michaelld
     Type:  defect      |     Status:  new
 Priority:  Normal      |  Milestone:
Component:  ports       |    Version:
 Keywords:              |       Port:  gr-lora
------------------------+-----------------------
 gr-lora changes the version in a variant.

 {{{
 $ port info gr-lora +rpp0 | head -n 1
 gr-lora @20170920 (science, comms)
 $ port info gr-lora +BastilleResearch | head -n 1
 gr-lora @20170713 (science, comms)
 $
 }}}

 Ports should not do this because it doesn't work the way users expect.
 Only the version corresponding to the default variants gets recorded in
 the portindex, and only the portindex is used when determining if a port
 is outdated. For example if I install with the +BastilleResearch variant:

 {{{
 $ sudo port install gr-lora +BastilleResearch
 --->  Computing dependencies for gr-lora
 --->  Fetching archive for gr-lora
 --->  Attempting to fetch gr-lora-
 20170713_0+BastilleResearch.darwin_16.x86_64.tbz2 from
 https://packages.macports.org/gr-lora
 --->  Fetching distfiles for gr-lora
 --->  Verifying checksums for gr-lora
 --->  Extracting gr-lora
 --->  Configuring gr-lora
 --->  Building gr-lora
 --->  Staging gr-lora into destroot
 --->  Installing gr-lora @20170713_0+BastilleResearch
 --->  Activating gr-lora @20170713_0+BastilleResearch
 --->  Cleaning gr-lora
 $
 }}}

 It is currently at an older version than the default +rpp0 variant, so it
 is immediately considered outdated, but upgrading does nothing:

 {{{
 $ port outdated gr-lora
 The following installed ports are outdated:
 gr-lora                        20170713_0 < 20170920_0
 $ sudo port upgrade gr-lora
 $
 }}}

 On the other hand, if the +BastilleResearch variant were at a newer
 version than the default +rpp0 variant, the port would not be displayed at
 all in the output of `port outdated` even when it is updated and the user
 would never know about the new version.

 If the user really needs to be given the choice of using the rpp0 or
 BastilleResearch forks, maybe it should be implemented as subports instead
 of variants.

--
Ticket URL: <https://trac.macports.org/ticket/55286>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list