On Tue, 2016-05-31 at 02:30 +0100, Ken Moffat wrote: > And now you seem to think it will be trivial for us to initially > add a list of packages which can use this package, and on subsequent > edits review that list for things which have dropped out or started > to use this (arguably, if we did that then additions should be added > when a package starts to use a dependency iff that dependency has a > list of packages which can use it.. Also, that list will waste a lot > of space on the page.
Note that he's not asking for any information that isn't already in the book - if Firefox can list a dependency on Gtk3, then we know that for Gtk3, Firefox is a package that requires it. I can't see that it's a huge ongoing burden for editors - but it does require a bunch of clever scripting to automatically generate the reverse-dependencies from the dependencies, and to incorporate that into the book. And yeah, I agree it would mostly be waste space in the book. I don't see the use-case for it... what's the benefit in looking at Gtk3, and seeing a list of some dozens of packages that I can build once I've installed that one? Simon.
signature.asc
Description: This is a digitally signed message part
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
