#675 Updated guidelines for per-edition divergent config
Closed: Fixed None Opened 2 years ago by sgallagh.

A recent [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/BX5ICSBX3NU6P3LCUUYJLAWZFHRMUGX7/ thread on Fedora Devel] made it clear that the current per-edition guidelines could use a little updating.

In particular, we originally mandated symlinking from the variant config to the real destination, but did not specify where to keep the variant configs. I've clarified this and also added that it is acceptable to copy a config on initial install instead of symlinking. The original reason for symlinks was to allow for auto-switching the config if the system converted to a different edition, but this was dangerous and ultimately it was decided not to allow that. So, copying is safe.

Proposed change:
https://fedoraproject.org/w/index.php?title=Sgallagh%3APer-Product_Configuration&diff=485317&oldid=485316


We discussed this at this weeks meeting (http://meetbot.fedoraproject.org/fedora-meeting-1/2017-02-09/fpc.2017-02-09-17.01.txt):

  • 675 Updated guidelines for per-edition divergent config (geppetto,


    17:41:20)
  • ACTION: Updated guidelines for per-edition divergent config (+1:5,
    0:0, -1:0) (geppetto, 18:12:56)

I've written these up. While looking at the document, the following additional points occurred to me:

  • The Definitions section at the top doesn't mention atomichost but it lists the other three variants.
  • The Definitions section defines "$PRODUCT" but this doesn't appear anywhere else in the document. I think that is some old text which these days has been replaced by $VARIANT_ID.
  • The definition of Fedora.next occurs after all of the actual uses of the term.
  • If you're looking for a definition of Fedora.next, if that's what we're even still calling it, this isn't the page you're looking for.

Given those and the fact that this is really not the best place to define "Fedora.next", I've just removed the entire definitions section. I'll put it back if someone yells at me.

Written up. Announcement text:

The guidelines for per-product configuration have been updated to allow copying the config file instead of mandating symlinking and to specify the locacation where the variant configurations should be stored.

I managed to write up the original diff without any of the later changes. I believe I fixed it all up, please please let me know if I missed anything.

Metadata Update from @tibbs:
- Issue assigned to tibbs

2 years ago

Login to comment on this ticket.

Metadata