Randy McMurchy wrote: > I've always thought that there should be some reference to the project's > home page for each of the BLFS packages. And for most we do, simply because > the download URL for most of the packages contain a reference to the base > URL. For those packages that the download URL is different than the > package home page, then yes, a reference would be acceptable.
This should be pretty easy. I'd suggest: + <!ENTITY ex-home "http://...";> ... <bridgehead renderas="sect3">Package Information</bridgehead> <itemizedlist spacing="compact"> + <listitem> + <para>Home page: <ulink url="&ex-home;"/></para> + </listitem> <listitem> <para>Download (HTTP): <ulink url="&ex-download-http;"/></para> </listitem> <listitem> <para>Download (FTP): <ulink url="&ex-download-ftp;"/></para> </listitem> <listitem> <para>Download MD5 sum: &ex-md5sum;</para> </listitem> <listitem> <para>Download size: &ex-size;</para> </listitem> <listitem> <para>Estimated disk space required: &ex-buildsize;</para> </listitem> <listitem> <para>Estimated build time: &ex-time;</para> </listitem> </itemizedlist> If we just agree to add this as we update a page, it would be beneficial. We don't have to go through all the packages right now and add it for every package. An incremental update would be reasonable. One minor problem would be the situation where a package may not have an individual home page. For instance, I'm pretty sure that not all Gnu packages have a dedicated home page. The issue would be what to use in those cases, if anything. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
