Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: moving recipe back to a directory available on the host #36

Closed
xynydev opened this issue Apr 23, 2023 · 4 comments · Fixed by #47
Closed

fix: moving recipe back to a directory available on the host #36

xynydev opened this issue Apr 23, 2023 · 4 comments · Fixed by #47

Comments

@xynydev
Copy link
Member

xynydev commented Apr 23, 2023

Currently the just setup-flatpaks command is broken (because of e9c31ab). In light of this, the recipe should probably be moved to some folder accessible on the host computer.

That folder probably shouldn't be /etc/, though, as that implies that it's a config file that can be edited, when it should only be changed inside the git repository.

@z0rrn
Copy link

z0rrn commented Apr 23, 2023

I like the concept of /.well-known/ so maybe we should copy it to /well-known/ (without the dot). There it would be accesibke for everyone.
Or is there a standart directory for package files? Like we use the package name ublue-os.

@xynydev
Copy link
Member Author

xynydev commented Apr 26, 2023

Isn't well-known related to webserves and SSL? I'd prefer a standard Linux root directory. I'm thinking just /usr/ would do. /usr/ublue-recipe.yml.

Or is there a standart directory for package files? Like we use the package name ublue-os.

/opt/ ig... This is not a package file, though.

@z0rrn
Copy link

z0rrn commented Apr 26, 2023

Or /var/ because it's a file that can change.
I think that /usr/ is bad because I read that it is also for programs.

@xynydev
Copy link
Member Author

xynydev commented Apr 26, 2023

Or /var/ because it's a file that can change. I think that /usr/ is bad because I read that it is also for programs.

Var is not something we can write to, and the file shouldn't be changed by the user on the computer (does nothing), only in git.

/usr/ I think is our only choice then, but it doesn't normally contain config files. Maybe /usr/etc/ could just do, which is basically the same as putting it in /etc/. Then just add a warning for users to not change the file on their system...

Not just putting it to /etc/ straight away was probably overthinking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants