Projects
New Ticket     Wiki     Browse Source     Timeline     Roadmap     Bug Reports     Search

Ticket #14141 (closed defect: fixed)

Opened 10 months ago

Last modified 9 months ago

Guide should say what characters are valid in variant names

Reported by: ryandesign@… Owned by: markd@…
Priority: Normal Milestone: Website & Documentation
Component: guide Version: 1.6.0
Keywords: Cc:
Port:

Description

Variant names may not contain a hyphen. (For example: "variant no-x11" would be wrong.) Underscores should be used instead (e.g. "variant no_x11"). The guide should mention this in the section on writing portfiles.

Change History

Changed 10 months ago by markd@…

  • status changed from new to closed
  • resolution set to fixed

I made modifications in #33664, #33665, and #33666. I'm closing the ticket, but feel free to critique the mods and reopen to make further suggestions if you like. There is always room for improvement. Thanks for catching this!

Changed 10 months ago by ryandesign@…

  • status changed from closed to reopened
  • resolution fixed deleted
  • summary changed from Variant names cannot contain hyphens; guide should mention this to Guide should say what characters are valid in variant names

Thanks for your quick response!

But actually, rather than just mention that the hyphen is invalid, let's mention what is valid. All our ports' variant names right now use just the letters A-Z and a-z, numbers 0-9 and the underscore, so I think that's the list of valid characters we should publish in the guide. It's still worth mentioning specifically that the hyphen is invalid, since people seem to want to use that, and a handful of ports' variant names still use the hyphen; I'll work with those port maintainers to remove those.

Related: port lint should warn on illegal variant names; see #14147.

Changed 10 months ago by markd@…

Okay, take a look at r33774 and r33775 and see how that looks.

Changed 9 months ago by markd@…

  • status changed from reopened to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.