View previous topic :: View next topic |
Author |
Message |
jgaz n00b
Joined: 14 Feb 2021 Posts: 42
|
Posted: Wed Mar 30, 2022 2:26 pm Post subject: [wiki] Article Name Collisions for Packages and Binaries |
|
|
I recently wrote the gzip article for the wiki. It's just a stub, but it's a start and others have already begun adding contributions to it. It's always a nice feeling to see others build on my work. While doing some research for another article, it occurred to me that the documentation link on app-arch/gzip just searches for gzip and loads the first exact match it finds. So, I need to write an article that is both about the package itself — which has something like 10 or 12 binaries in it — and the gzip command proper.
Are there rules for this kind of situation?
The way I see it, I should write a document about the package itself, document the use flags, and have a table of all of the binaries it contains. Then have links to articles for each binary in the package. Where the article name conflicts, have a separate article for "gzip_(command)" or something like that. Thoughts? |
|
Back to top |
|
|
charles17 Advocate
Joined: 02 Mar 2008 Posts: 3664
|
Posted: Thu Mar 31, 2022 1:42 pm Post subject: Re: [wiki] Article Name Collisions for Packages and Binaries |
|
|
jgaz wrote: | Are there rules for this kind of situation? | I'm not aware of any such rules. Even ebuild has only one artice both for the command and file format.
But why at all did you put emerge and unmerge sections for an @system package? |
|
Back to top |
|
|
jgaz n00b
Joined: 14 Feb 2021 Posts: 42
|
Posted: Thu Mar 31, 2022 1:56 pm Post subject: |
|
|
Thanks for the feedback.
I was just being through. I should probably add a note to the effect of, "while you can umerge this package doing so is a bad idea as it's a core part of the system." |
|
Back to top |
|
|
charles17 Advocate
Joined: 02 Mar 2008 Posts: 3664
|
Posted: Fri Apr 01, 2022 1:37 pm Post subject: |
|
|
Also Installation. Isn't it part of Stage 3? |
|
Back to top |
|
|
|