Talk:Gentoolkit

euse -a output
euse -a In the output there is sometimes the letter F instead of G. Reader cannot find the meaning even in "man euse".


 * Whats Reader? Post an example, capital F is usually FORCE under most nix based systems. - Killerc (talk) 03:51, 15 June 2014 (UTC)

euse
This needs updating on the euse side i believe.

(Don't question why i use this i know its a mess but this is why its a good example)

Most of these are set globally, but the final column; berkdb xmlrpc, bzip2 etc is not explained. Also some things are listed twice, i very very rarely use the - flag on anything as its not needed for my installed system, yet things like: xmlrpc             [-      ] (xmlrpc) xmlrpc             [-      ] (xmlrpc) are listed twice, without any explanation as to why other than its a -, its obviously listed in 2 different files/locations where the flags are set but which? - Killerc (talk) 03:52, 15 June 2014 (UTC)

equery
Shouldn't the whole section about equery be moved to equery (merge the info into the page dedicated to it)? Same with the other invocations. Augustin (talk) 14:30, 27 February 2015 (UTC)


 * Hi Augustin, in my opinion what you're proposing seems viable. The Gentoolkit article is not even close to explaining all the tools that come with it. If the same amount of detailed explanation is given to the other tools then the Gentoolkit article would be way too long for one article... It seems to me that one option would be to nest the Equery article under the Gentoolkit article (Gentookit/Equery) via a sub-article. This method could be used with other tools since they are part of Gentoolkit as well (Gentoolkit/euse, etc). Another option is to just link the specific tool articles back to the main Gentoolkit article (like the existing Equery article). I guess this might be something to ask on the Suggestions page.


 * If a package contains more than one tool, should the tool usage be covered on the package's article? Or should each tool be in a sub-article? --Maffblaster (talk) 21:12, 12 March 2015 (UTC)


 * I agree, if a page becomes very large and contains enough information to be split, then it makes sense to split it. The "master" page can then just have a small introduction to a tool and refer to the dedicated page for more information.
 * On the dedicated page, I would use a disconnected page (not a subpage). Subpages should be used when the information still matches the master page, but has been split due to the size. For instance, a subpage for troubleshooting of a tool, or for a reference list of parameters. --SwifT (talk) 18:41, 2 March 2015 (UTC)

revdep-rebuild
The command has been rewritten in Python. The old Bash version has been renamed to. In my opinion we should update the example in this article using the newer Python version. Weird question: how can I safely break my system in order to get some nice output for this article? Fturco (talk) 11:53, 12 May 2017 (UTC)


 * Good question.
 * However I seem to have one package needing rebuilding, so here's the output:


 * You may want to use RootCmd template instead. I used RootInvocation here to save some space. --Zucca (talk) 13:18, 12 May 2017 (UTC)


 * If you intentionally want to break something for for revdep-rebuild to repair, on a graphical system, could try running something like:
 * You should be able to run the above command on any library that is a linked dependency of any other library. You can look at linking using the command on a  file. You can thank  for the example command above. --Maffblaster (talk) 23:26, 20 January 2022 (UTC)
 * You should be able to run the above command on any library that is a linked dependency of any other library. You can look at linking using the command on a  file. You can thank  for the example command above. --Maffblaster (talk) 23:26, 20 January 2022 (UTC)