You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 19, 2021. It is now read-only.
So I was reviewing section 3 of the book and found a spot that I had to read over again a couple of times to clarify it and I thought I'd offer it as feedback where someone might find it confusing if they're new(ish) to EPM.
In Document '3-Packaging':
[ Huge chunk cut for discussion.... ]
d 755 root sys /var/spool/foo -
Finally, symbolic links use the letter l (lowercase L) for the type field:
l 000 root sys /usr/bin/foobar foo
The source field specifies the file to link to and can be a relative path.
Question that arises when reading this...
What frame of reference do we use for 'foo'?
Is it 'foo' when the package is built or 'foo' when the package is being installed?
I'm of the opinion that the doc should clarify that statement including, if it's the second choice above, then where's that 'foo' live? What path is it grabbing it from? Relative to what?
Yes, I'm aware that with lots of experience this becomes much more clear but until then we're confused.
Wildcards
Wildcard patterns can be used in the source field to include multiple
files on a single line:
f 0444 root sys /usr/share/doc/foo *.html
This is actually not clear to me.
Even with my experience using EPM, I find it hard to read.
Does this say "Any 'html' file you find install it as '/usr/share/doc/foo'" (Which makes no sense, many to one.) OR
Does it say "In the directory 'foo' under '/usr/share/doc' create a link for every 'html' file in our current path?"
(Which is what I assume.)
I would request a little more verbiage on this.
It might be sufficient to clarify it with a line above that saying
"d 0555 root sys /usr/share/doc/foo -"
to make it clearer about what's being created but I'm not sure yet.
Thank you for your indulgence.
The text was updated successfully, but these errors were encountered:
So I was reviewing section 3 of the book and found a spot that I had to read over again a couple of times to clarify it and I thought I'd offer it as feedback where someone might find it confusing if they're new(ish) to EPM.
In Document '3-Packaging':
[ Huge chunk cut for discussion.... ]
Finally, symbolic links use the letter
l
(lowercase L) for the type field:The source field specifies the file to link to and can be a relative path.
Question that arises when reading this...
What frame of reference do we use for 'foo'? Is it 'foo' when the package is built or 'foo' when the package is being installed?
I'm of the opinion that the doc should clarify that statement including, if it's the second choice above, then where's that 'foo' live? What path is it grabbing it from? Relative to what?
Yes, I'm aware that with lots of experience this becomes much more clear but until then we're confused.
Wildcards
Wildcard patterns can be used in the source field to include multiple files on a single line:
This is actually not clear to me. Even with my experience using EPM, I find it hard to read. Does this say "Any 'html' file you find install it as '/usr/share/doc/foo'" (Which makes no sense, many to one.) OR Does it say "In the directory 'foo' under '/usr/share/doc' create a link for every 'html' file in our current path?" (Which is what I assume.)
I would request a little more verbiage on this.
It might be sufficient to clarify it with a line above that saying
Thank you for your indulgence.
The text was updated successfully, but these errors were encountered: