Skip to content
This repository was archived by the owner on Oct 19, 2021. It is now read-only.

Question from docs... (Last one! I promise.) #77

Closed
MichaelTiernan opened this issue Mar 13, 2020 · 2 comments
Closed

Question from docs... (Last one! I promise.) #77

MichaelTiernan opened this issue Mar 13, 2020 · 2 comments
Assignees
Labels
Milestone

Comments

@MichaelTiernan
Copy link
Contributor

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.

@michaelrsweet
Copy link
Owner

@MichaelTiernan I'll make some clarifications. FYI:

  • For symlinks, relative paths are relative to the destination, just as if you typed "ln -s foo /path/to/bar"

  • For wildcards, the files go in /usr/share/doc/foo/filename.html; I'll expand the example to show this explicitly.

@michaelrsweet
Copy link
Owner

[master 0dda975] Update symlink and wildcard discriptions (Issue #77)

@michaelrsweet michaelrsweet self-assigned this Mar 13, 2020
@michaelrsweet michaelrsweet added this to the Stable milestone Mar 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants