Add fallback for /etc

[9p4]

If there is no config found, fallback to a system-wide config in /etc/meow.conf

[faynopi]

We do not produce configuration at /etc/meow.conf by default; instead, it is generated in $HOME/.meow.conf or $XDG CONFIG HOME/meowfetch/meow.conf. As a result, we don't require a backup for it.

At the parser function, we additionally check to see if a directory exists.
https://github.com/Itsnexn/meowfetch/blob/b1274473994a072854ce663fa5f4b1b434beaec6/configs/config.go#L53
As a result, I don't believe we need a fallback value for this function.

[9p4]

There is an application for this. When calling meowfetch as part of a motd script, the script does not have environment variables initialized. Since the os.UserHomeDir and os.LookupEnv both use environment variables to get the location of the configuration, there ought to be a way for the system to fallback to a system-wide config.

https://pkg.go.dev/os#UserHomeDir

[faynopi]

When calling meowfetch as part of a motd script, the script does not have environment variables initialized.

I don't understand what you mean by motd script.

Since the os.UserHomeDir and os.LookupEnv both use environment variables to get the location of the configuration, there ought to be a way for the system to fallback to a system-wide config.

there is no system-wide configuration. the program will generate config by itself if it does not exist.

https://github.com/Itsnexn/meowfetch/blob/b1274473994a072854ce663fa5f4b1b434beaec6/configs/config.go#L52-L70

please open an issue about this problem and we could continue this conversation there.

I think the best approach would be to copy the config file using the makefile at the install time. we could remove the embed and then change the parser.

[9p4]

Continuing in #5