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

Introduction should clarify that hashes are used in paths to software #7

Open
tejing1 opened this issue Aug 21, 2022 · 2 comments
Open

Comments

@tejing1
Copy link

tejing1 commented Aug 21, 2022

This section:

This information is aggregated through hashing, and allows nix to
describe and reference the exact software which is intended to use.
This enables nix to be used on any system because it's assumptions
do not collide with the assumptions of a host system. This also means that
nix does not adhere to the traditional [File Hierarchical System(FHS)](https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard)
but it also means that it's not limited to FHS's restriction of only having
a single variant of a piece of software.

is difficult to follow because no mention has yet been made that hashes are used to determine the paths at which software is installed. Many of the claims in this paragraph don't make sense without that context.

@tejing1 tejing1 changed the title Introduction should clarify that hashes are used to in paths to software Introduction should clarify that hashes are used in paths to software Aug 21, 2022
@jonringer
Copy link
Collaborator

;( Fair, I'll think about how to word this in a more clear way.

@tejing1
Copy link
Author

tejing1 commented Aug 22, 2022

The first few paragraphs are the hardest to get right, but also the most important. I'm sure it'll take some iterating.

Is it enough to just make it:

This information is aggregated through hashing, and used to determine the software's installation path, allowing nix to describe...

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

No branches or pull requests

2 participants