Kill etc/config.fish

[faho]

(Sorry, I know this is a bit late)

Like @amluto asked for in #2498, remove etc/config.fish by appending the code to share/config.fish.

This improves life for packagers as there's one less file in etc (thought of as user/admin territory in recent years). Also there's one less file for us to worry about.

It might be nice to nix these two remaining things entirely but I'm not too sure about that.

While I was at it, I've also stringified it, which is why I'd like a quick check from someone else.

[krader1961]

lgtm

[zanchey]

Perhaps we should leave a skeleton file in etc/config.fish - something along the lines of:

# config.fish
# Put system-wide fish configuration entries here
# or in .fish files in conf.d/

# This file is run by all fish instances.
# To include configuration only for login shells, use
# if status --is-login
#    ...
# end
# To include configuration only for interactive shells, use
# if status --is-interactiv
#   ...
# end

[faho]

@zanchey: If I understand correctly, packagers would prefer not to have files in /etc at all (for "stateless systems" and to have one less file to backup if it changed), so that would kind of defeat the point.

Though we should probably still create the directory.

@amluto: Did I get that right?

[amluto]

A bunch of the actual empty-/etc stuff is being done in the OSTree project,
and I don't know too much about the fine details. But I don't have a
strong preference between omitting the file and leaving in a placeholder.
As long as fish is fully functional without anything in /etc, everyone wins
:)

On Mon, Mar 7, 2016 at 4:13 AM, Fabian Homborg notifications@github.com
wrote:

@zanchey https://github.com/zanchey: If I understand correctly,
packagers would prefer not to have files in /etc at all (for "stateless
systems" and to have one less file to backup if it changed), so that would
kind of defeat the point.

Though we should probably still create the directory.

@amluto https://github.com/amluto: Did I get that right?

—
Reply to this email directly or view it on GitHub
#2799 (comment)
.

[zanchey]

r+ - go ahead and merge.

As a packager I'm not fussed by no-op files, but as a systems admin I'd like to have a template or example available.

[faho]

Merged as 6288f89. Thanks!