automating FLOSS software listings
LM <[email protected]> Thu, 20 Jun 2019 12:56:47 -0400
| Newsgroups | gmane.linux.lfs.general |
|---|---|
| Message-ID | <CAFipMOH9sCh=OMHCJS8Mduhmz_8wTs=Cvad_7oS7rKA1hNXCYQ@mail.gmail.com> |
Has anyone thought about auto-generating a list of the software that's installed on their LFS system in a format that's friendly to end users? We've extracted the Schoolforge FLOSS software list from a database to CSV format. The Schoolforge project currently has over 300 programs in the list. The new site design won't include a database. So, we've been thinking of converting the information to another format like PDF, wiki, GitHub list, etc. We're trying to share information about interesting and useful FLOSS software with people who may not be that familiar with it or may not know what's available out there. I've also been experimenting with adding documentation utilities to the build tools I use when doing BLFS builds. Was thinking it would be fun to share information and descriptions of the FLOSS I like to build from scratch on my system. At this point, I'm debating whether I should try to use the documentation utilities from my build tools (still a work in progress) or whether there's an easier and more effective route to share this type of information with end users. Assuming I convert the Schoolforge software information to a format my build system can handle, I can currently output to HTML (or other text format) using a template based document creation system. From HTML, I can use wkhtmltopdf to convert to PDF. wkhtmltopdf can auto-generate a table of contents. I still would like to work on an automated way to generate an index based on keywords. Has anyone attempted a project like this for their on LFS/BLFS system? Does anyone have recommendations of useful Linux/Unix style command line tools/scripts for working with text files (especially creating indexes) beyond the standard coreutils? Are there more efficient ways to get an easy to read FLOSS software list document generated from CSV? If you've worked on a similar software documentation project or have ideas on a good way to accomplish something like this, would appreciate hearing about it. Thanks. -- http://lists.linuxfromscratch.org/listinfo/lfs-chat FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page