cvs commit: www/test/lfs packages.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Mon Aug 25 06:05:55 PDT 2003


jeroen      03/08/25 07:05:55

  Modified:    test     sitemap.html website-bottom.html
               test/hints acknowledgements.html adoptahint.html
                        hints-template.html howtowrite.html list.html
                        news-bottom.html submit.html whatarehints.html
               test/lfs packages.html
  Log:
  Updated the hints format rules and submission guidelines according to the latest specs by Tushar. Also integrated his comments on this and spell fixes. Renamed a rather long menu entry to just Write a hint. Small adjustments to the lfs packages page and the website's acknowledgements.
  
  Revision  Changes    Path
  1.28      +1 -1      www/test/sitemap.html
  
  Index: sitemap.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/sitemap.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  --- sitemap.html	22 Aug 2003 16:05:33 -0000	1.27
  +++ sitemap.html	25 Aug 2003 13:05:54 -0000	1.28
  @@ -155,7 +155,7 @@
   					<li><a href="hints/index.html">Hints mirrors</a></li>
   					<li><a href="hints/news.html">Hints News</a></li>
   					<li><a href="hints/whatarehints.html" title="What are these hints for?">What are LFS hints?</a></li>
  -					<li><a href="hints/howtowrite.html" title="Style and format of hints">How do I write LFS hints?</a></li>
  +					<li><a href="hints/howtowrite.html" title="Style and format guidelines of hints">Write a hint</a></li>
   					<li><a href="hints/adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   					<li><a href="hints/submit.html" title="If you want to submit a new hint">Submit new hint</a></li>
   					<li><a href="hints/acknowledgements.html" title="People who earned credits for their contributions">Acknowledgements</a></li>
  
  
  
  1.10      +8 -7      www/test/website-bottom.html
  
  Index: website-bottom.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/website-bottom.html,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- website-bottom.html	23 Aug 2003 09:05:33 -0000	1.9
  +++ website-bottom.html	25 Aug 2003 13:05:54 -0000	1.10
  @@ -50,15 +50,16 @@
   	<p>The following people and organisations have been more than a great help while creating this website:</p>
   	<ul>
   		<li>Gerard Beekmans, for giving me all the trust, freedom and resources necessary to do this</li>
  -		<li>Anderson Lizardo, for writing the scripts which form the backbone of the news pages, for managing the <a href="http://lfs-br.codigolivre.org.br/">Portugese translation</a> and for general testing and feedback.</li>
  -		<li>Craig Colton and Wout van Heeswijk for submitting great logo's</li>
  -		<li>Rob Park, for suggesting the RSS feeds and providing the means to do them</li>
  -		<li>Bill W. Maltby, for his efforts to minimise lingual errors</li>
  -		<li>Johan Lenglet, for running the French translation</li>
  -		<li>Manuel Canales Esparcia, for running the Spanish translation</li>
  +		<li>Anderson Lizardo, for writing the scripts which form the backbone of the news pages, for managing the <a href="http://lfs-br.codigolivre.org.br/">Portugese translation</a> and for general testing and feedback</li>
  +		<li>Craig Colton and Wout van Heeswijk for submitting <a href="http://test.linuxfromscratch.org/blfs/artwork/logo/">great logo's</a></li>
  +		<li>Rob Park, for suggesting the <a href="http://test.linuxfromscratch.org/lfs/feed.rss">RSS feeds</a> and providing the <a href="http://cvs.linuxfromscratch.org/index.cgi/www/test/lfs2rss.pl?sortby=rev">means</a> to do them</li>
  +		<li>Bill Maltby, for his efforts to minimise lingual errors</li>
  +		<li>The French team, for running the <a href="http://www.fr.linuxfromscratch.org/">French translation</a></li>
  +		<li>Manuel Canales Esparcia, for running the <a href="http://www.escomposlinux.org/lfs-es/">Spanish translation</a></li>
   		<li>Jeremy Utley, for helping with the <a href="../lfs/packages.html">P2P initiative</a> and his general support</li>
  +		<li>The creator and maintainer of <a href="http://www.red-bean.com/cvs2cl/">cvs2cl</a>, without which we couldn't provide daily CVS information</li>
   		<li>The LFS community, for which this is made</li>
  -		<li>The css-discuss and webdesign-l mailing lists, for checking the site for errors</li>
  +		<li>The <a href="http://www.css-discuss.org/">css-discuss</a> and <a href="http://www.webdesign-l.com/">webdesign-l</a> mailing lists, for checking the site for errors</li>
   		<li>Everybody else who had suggestions, tested the site or silently approves of it :)</li>
   	</ul>
   
  
  
  
  1.20      +1 -1      www/test/hints/acknowledgements.html
  
  Index: acknowledgements.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/acknowledgements.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- acknowledgements.html	21 Aug 2003 19:15:01 -0000	1.19
  +++ acknowledgements.html	25 Aug 2003 13:05:55 -0000	1.20
  @@ -71,7 +71,7 @@
   		<ul>
   		<li><a href="news.html">Hints News</a></li>
   		<li><a href="whatarehints.html" title="What are these hints for?">What are LFS hints?</a></li>
  -		<li><a href="howtowrite.html" title="Style and format of hints">How do I write LFS hints?</a></li>
  +		<li><a href="howtowrite.html" title="Style and format guidelines of hints">Write a hint</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   		<li><a href="submit.html" title="If you want to submit a new hint">Submit new hint</a></li>
   		<li><a href="acknowledgements.html" title="People who earned credits for their contributions" class="currentpage">Acknowledgements</a></li>
  
  
  
  1.22      +1 -1      www/test/hints/adoptahint.html
  
  Index: adoptahint.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/adoptahint.html,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- adoptahint.html	21 Aug 2003 19:15:01 -0000	1.21
  +++ adoptahint.html	25 Aug 2003 13:05:55 -0000	1.22
  @@ -72,7 +72,7 @@
   		<ul>
   		<li><a href="news.html">Hints News</a></li>
   		<li><a href="whatarehints.html" title="What are these hints for?">What are LFS hints?</a></li>
  -		<li><a href="howtowrite.html" title="Style and format of hints">How do I write LFS hints?</a></li>
  +		<li><a href="howtowrite.html" title="Style and format guidelines of hints">Write a hint</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint" class="currentpage">Adopt a hint</a></li>
   		<li><a href="submit.html" title="If you want to submit a new hint">Submit new hint</a></li>
   		<li><a href="acknowledgements.html" title="People who earned credits for their contributions">Acknowledgements</a></li>
  
  
  
  1.20      +1 -1      www/test/hints/hints-template.html
  
  Index: hints-template.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/hints-template.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- hints-template.html	21 Aug 2003 19:15:01 -0000	1.19
  +++ hints-template.html	25 Aug 2003 13:05:55 -0000	1.20
  @@ -65,7 +65,7 @@
   		<ul>
   		<li><a href="news.html">Hints News</a></li>
   		<li><a href="whatarehints.html" title="What are these hints for?">What are LFS hints?</a></li>
  -		<li><a href="howtowrite.html" title="Style and format of hints">How do I write LFS hints?</a></li>
  +		<li><a href="howtowrite.html" title="Style and format guidelines of hints">Write a hint</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   		<li><a href="submit.html" title="If you want to submit a new hint">Submit new hint</a></li>
   		<li><a href="acknowledgements.html" title="People who earned credits for their contributions">Acknowledgements</a></li>
  
  
  
  1.22      +36 -57    www/test/hints/howtowrite.html
  
  Index: howtowrite.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/howtowrite.html,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- howtowrite.html	21 Aug 2003 19:15:01 -0000	1.21
  +++ howtowrite.html	25 Aug 2003 13:05:55 -0000	1.22
  @@ -41,67 +41,46 @@
   	<em><a href="#projectnav" class="hidden">Skip to subproject-navigation</a></em>
   	<em><a href="#generalnav" class="hidden">Skip to sitewide navigation</a></em>
   
  -	<h2>How to write a hint</h2>
  -		<p>Anyone can submit an lfs-hint. We'll list some general rules and guidelines for writing hints, and offer you some technical details on how to layout the hint.</p>
  -		<p>A good hint provides information which is not otherwise easily obtainable. In general, we're not interested in hints which copy information already in LFS or BLFS and hints which simply list the steps needed for installing a package as explained in the INSTALL or README of a package.</p>
  -		<p>This leaves a broad scope of subjects. Hints can be about everything for which a non-obvious or non-trivial fix or hack is required. A hint can also explain a complicated package installation or a particular setup. Have a look at some <a href="list.html">other hints</a> to get an idea of what a hint may include.</p>
  -		<p>Once you have a good and original idea for a hint, you can start writing. Stick to the following style rules if you want to <a href="submit.html">submit</a> it for inclusion.</p>
  -		<ol>
  -			<li><a href="#hintformat">Hint format</a></li>
  -			<li><a href="#description">Description</a></li>
  -			<li><a href="#restrictions">Restrictions</a></li>
  -			<li><a href="#filename">Filename</a></li>
  -			<li><a href="#license">License</a></li>
  -			<li><a href="#revision">Revision</a></li>
  -		</ol>
  +<h2>How to write a hint</h2>
  +	<p>Anyone can submit an lfs-hint. We'll list some general rules and guidelines for writing hints, and offer you some technical details on how to layout the hint.</p>
  +	<p>A good hint provides information which is not otherwise easily obtainable. In general, we're not interested in hints which copy information already in LFS or BLFS and hints which simply list the steps needed for installing a package as explained in the INSTALL or README of a package.</p>
  +	<p>This leaves a broad scope of subjects. Hints can be about everything for which a non-obvious or non-trivial fix or hack is required. A hint can also explain a complicated package installation or a particular setup. Have a look at some <a href="list.html">other hints</a> to get an idea of what a hint may include.</p>
  +	<p>Once you have a good and original idea for a hint, you can start writing. Stick to the following style rules if you want to <a href="submit.html">submit</a> it for inclusion.</p>
   
  -		<h3 id="hintformat">Hint Format</h3>
  +	<h3 id="hintformat">Hint Format</h3>
  +		<p>Every hint should have the following sections, in the order specified here so as to have a consistent look and feel:) Check out the <a href="files/hint_sample.txt">example hint</a>.</p>
  +	<dl>
  +		<dt>AUTHOR:</dt>
  +			<dd>This field can be repeated if there are multiple authors. Each author line should have name and contact details of the hint author.</dd>
  +		<dt>DATE:</dt>
  +			<dd>The date the hint was last updated in international format (YYYY-MM-DD).</dd>
  +		<dt>LICENSE:</dt>
  +			<dd>The license under which the hint is licensed. The hint maintainers suggest GNU Free Documentation License, but you are free to choose your own. The GNU Free Documentation License allows copying of your hint and modifying it without restriction, with the exception that you will always be credited as author. It also indicates that the hint carries no guarantees. For more information on various licenses, visit <a href="http://www.gnu.org/philosophy/license-list.html">the GNU website</a>.</dd>
  +		<dt>SYNOPSIS:</dt>
  +			<dd>A one line description about the hint. Please keep this short and sweet and restrict it to a single line since this is the title that would be included on the hints page.</dd>
  +		<dt>PRIMARY URI:</dt>
  +			<dd>This is an optional section for authors who like to host their own hints and only submit ocassional updates to the official hints site.</dd>
  +		<dt>DESCRIPTION:</dt>
  +			<dd>A short description on why the hint was written, who is the target audience, etc. This would help a user in determining whether the hint is useful for her/him.</dd>
  +		<dt>PRE-REQUISITES:</dt>
  +			<dd>In this section list the pre-requsites that the user needs to be aware of before following the hint. This section can be used to indicate if the hint is applicable only for a particular LFS version.</dd>
  +	<dt>HINT:</dt>
  +			<dd>This is the heart of the hint. List the details about your hint here. There is no restriction on how you format things in this section, except to avoid lines which look like a section (i.e. Text in all uppercase). Avoid including material that is already included in the book. </dd>
  +		<dt>ACKNOWLEDGEMENTS:</dt>
  +			<dd>Acknowledgements for people who have contributed to the hint. This section is optional.</dd>
  +		<dt>CHANGELOG:</dt>
  +			<dd>Include timestamped changes that have occured in the hint. Add latest entries at the end. Entries in this section should be as follows:<br />
   			<ul class="code">
  -				<li>TITLE:(2 tabs)  <title></li>
  -				<li>LFS VERSION:(1 tab) <version></li>
  -				<li>AUTHOR:(2 tabs)  <author name> <email address></li>
  -				<li> </li>
  -				<li>SYNOPSIS:(1 tab) </li>
  -				<li><synopsis></li>
  -				<li>HINT:</li>
  -				<li><hint></li>
  -				<li><License> (optional)</li>
  +				<li>[YYYY-MM-DD]</li>
  +				<li> * Changed A</li>
  +				<li> * Changed B</li>
   			</ul>
  +			In addition, if the changes are based a user's comments to you, mention the name/e-mail in the ChangeLog.</dd>
  +		</dl>
   
  -		<h3 id="description">Description</h3>
  -			<dl>
  -				<dt><title></dt>
  -					<dd>Short title of hint.</dd>
  -				<dt><version></dt>
  -					<dd>LFS version the hint applys to.	Examples are - 2.4.4, 2.4.4+ or All.</dd>
  -				<dt><author name></dt>	
  -					<dd>Name of author.</dd>
  -				<dt><email address></dt>
  -					<dd>The author's email address, enclosed in <> characters.</dd>
  -				<dt><synopsis></dt>
  -					<dd>Short description of the hint. Please keep this smaller than 3 lines</dd>
  -				<dt><hint></dt>
  -					<dd>The hint itself. No limit on size</dd>
  -				<dt><license></dt>
  -					<dd>The license under which this hint falls. If none specified, the <a href="http://www.gnu.org/licenses/licenses.html#TOCFDL">GNU Free Documenation License</a> is assumed</dd>
  -			</dl>
  -			<h3 id="restrictions">Restrictions</h3>
  -				<ol>
  -					<li>Lines must be a maximum of 80 characters long.</li>
  -					<li>Tab stop's should be set to a value of 8 spaces. This is usually the default but not everyone uses 8, some people use 4.</li>
  -					<li><code>./configure</code> commands must be in the style of the linuxfromscratch book (ie. the <code>./configure</code> command is followed by its parameters). When a <code>./configure</code> command exceeds the allowed width, use \ characters and indent the lines, except the first.</li>
  -				</ol>
  -
  -			<h3 id="filename">File name</h3>
  -				<p>The filename should be all in lower case and preferably only 1 word in length. If spaces are required, they should be replaced with the _ (underscore) character. If your hint follows these rules, you're ready to <a href="submit.html">submit</a> it.</p>
  -
  -			<h3 id="license">License</h3>
  -				<p>It may seem trivial but it's important to note that all hints you write will be protected by the <a href="http://www.gnu.org/licenses/licenses.html#TOCFDL">GNU documentation license</a>. This means that it may be copied and modified without restriction, with the exception that you will always be credited as author. It also means that the hint has no guarantee whatsoever. Should you require another license, please note this at the end of the hint.</p>
  -
  -			<h3 id="revision">Revision</h3>
  -				<p>This document is an extension of the WRITING_HINTS text which is also included in the hints tarball and directory. 
  -				<p>The original author was <a href="mailto:nomis80 at videotron.ca">Simon Perreault</a>. <a href="mailto:ian at ichilton.co.uk">Ian Chilton</a> has made some revisions and updates since he took over the hint maintainership, allthough that last position is now filled by <a href="mailto:timothy at linuxfromscratch.org">Timothy Bauscher</a>.</p>
  -				<p>The conversion to XHTML and addtion of the license requirement was done by <a href="mailto:jeroen at linuxfromscratch.org">Jeroen Coumans</a>.</p>
  +<h4>NOTE:</h4>
  +	<p>These instructions are based on responses from many users, in particular the following threads: <a href="http://archives.linuxfromscratch.org/mail-archives/hints/2003-June/001737.html">Expired and Outdated hints</a> and <a href="http://archives.linuxfromscratch.org/mail-archives/hints/2003-August/001828.html">Reorganization of hints</a>.</p>
  +	<p>If you have suggestions for improving this document, feel free to discuss it on the hints mailing list or drop a line to the hint maintainers at <a href="mailto:hints-owner at linuxfromscratch.org">hints-owner at linuxfromscratch.org</a>. The lfs-hints project is currently maintained by <a href="mailto:tushar at linuxfromscratch.org">Tushar Teredesai</a>.</p>
   
   </div> <!-- end content -->
   
  
  
  
  1.24      +1 -1      www/test/hints/list.html
  
  Index: list.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/list.html,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- list.html	21 Aug 2003 19:15:01 -0000	1.23
  +++ list.html	25 Aug 2003 13:05:55 -0000	1.24
  @@ -341,7 +341,7 @@
   		<ul>
   		<li><a href="news.html">Hints News</a></li>
   		<li><a href="whatarehints.html" title="What are these hints for?">What are LFS hints?</a></li>
  -		<li><a href="howtowrite.html" title="Style and format of hints">How do I write LFS hints?</a></li>
  +		<li><a href="howtowrite.html" title="Style and format guidelines of hints">Write a hint</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   		<li><a href="submit.html" title="If you want to submit a new hint">Submit new hint</a></li>
   		<li><a href="acknowledgements.html" title="People who earned credits for their contributions">Acknowledgements</a></li>
  
  
  
  1.4       +1 -1      www/test/hints/news-bottom.html
  
  Index: news-bottom.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/news-bottom.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- news-bottom.html	21 Aug 2003 19:15:01 -0000	1.3
  +++ news-bottom.html	25 Aug 2003 13:05:55 -0000	1.4
  @@ -22,7 +22,7 @@
   		<ul>
   		<li><a href="news.html" class="currentpage">Hints News</a></li>
   		<li><a href="whatarehints.html" title="What are these hints for?">What are LFS hints?</a></li>
  -		<li><a href="howtowrite.html" title="Style and format of hints">How do I write LFS hints?</a></li>
  +		<li><a href="howtowrite.html" title="Style and format guidelines of hints">Write a hint</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   		<li><a href="submit.html" title="If you want to submit a new hint">Submit new hint</a></li>
   		<li><a href="acknowledgements.html" title="People who earned credits for their contributions">Acknowledgements</a></li>
  
  
  
  1.22      +16 -4     www/test/hints/submit.html
  
  Index: submit.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/submit.html,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- submit.html	21 Aug 2003 19:15:01 -0000	1.21
  +++ submit.html	25 Aug 2003 13:05:55 -0000	1.22
  @@ -44,9 +44,21 @@
   <h2>Ready to submit</h2>
   	<p>So you've decided you want to enlighten us with a hint? And you want to submit it for inclusion? Great!</p>
   	<p><strong>Important: </strong>make sure you follow the <a href="howtowrite.html">rules</a> for writing a hint. Once you're satisfied with it, you're ready to submit.</p>
  -<h3>How to submit</h3>
  -	<p>To submit or update a hint, send an e-mail to the <a href="mailto:hints at linuxfromscratch.org">hint mailing list</a>. From there it will be picked up by the hint maintainer, who will update the hint index and the tarball. To check if your hint has already been included, you can <a href="../mail.html">subscribe</a> to the hints mailinglist, check its <a href="http://archive.linuxfromscratch.org/mail-archives/hints/">archive</a> or use the <a href="../newsgroups.html">news group</a> gateway. As soon as it's added it's also viewable from the <a href="list.html">list</a> and the <a href="files/">files</a> sections on this website.</p>
  -	<p>Keep the hints list solely for submitting hints and updates to hints. If you want to discuss or announce a new hint, <a href="mailto:blfs-support at linuxfromscratch.org">blfs-support</a> is a good forum.</p>
  +<h3>Submission guidelines</h3>
  +<ul>
  +	<li>Before submitting a hint, check if there is an already existing hint on the topic. If there is then contact the author if you have any updates. If the previous author is not interested in maintaining the hint, or if there is no response from the author for at least a month, then you may <a href="adoptahint.html">take over maintainence of the hint</a>. Remember to CC hints-owner at linuxfromscratch.org  regarding all correspondence with the author so that the hint maintainers are aware of the changeover.<br />
  +		<em>Note that this does not mean that duplicate hints on the same topic are not allowed. If you feel that the current author has a different approach to a problem and you have one which does not match the current hint, feel free to submit a separate hint. We suggest writing a short blurb on how the new hint differs from the existing one. Remember, the more information users have related to your hint, the more the chances of someone using the hint.</em></li>
  +	<li>Hints should be reserved for things that cannot be included into the book. Hints that relate to installation of packages and which would easily fit into the book (usually the BLFS book) should be submitted to the relevant development list.  We reserve the instructions and basic configuration for the book and leave the additional stuff such as advanced configuration and detailed explainations in a hint. If you are conversant with docbook and XML, then feel free to submit a patch to the current CVS Book version. If not, submit a text file matching the current format of the book and a book editor will do the neccessary modifications. </li>
  +	<li>If you are in the process of writing a hint on a topic, it would be good to drop a line to the relevant list in case someone else is working on something similar.</li>
  +	<li>A hint should not duplicate documentation that is already available elsewhere on a particular topic, it should complement it. Documentation available elsewhere includes <a href="http://www.tldp.org/">LDP documentation</a>, documentation available from the package website, documentation available by a simple <a href="http://www.google.com">google</a> search. Also, things that are already well documented in the book(s) or at the LDP should not be repeated in the hint unless the hint describes matters in more detail, in a different way, or from a different perspective. So things such as installation of db, freetype, zlib, etc can just be referenced by pointers to the book. </li>
  +	<li>Authors who are not interested in maintaining their hints any more should send a message to the hints mailing list specifying that the hint is <a href="adoptahint.html">up for adoption</a>. The author should also notify the hints list if the hint is not relevant anymore.</li>
  +	<li>Hints that have been integrated into the book will be retired after a stable version of the book is released.</li>
  +	<li>Keep the file name of the hint short, but descriptive. The extension for the hint should be .txt. The name should be all lowercase.</li>
  +	<li>The hint document is text based. The format for the hints is as explained at the end of this document.</li>
  +	<li>Avoid including scripts and patches in the hints. Submit these as separate files along with the hint submission and they will be hosted on a separate location for download. Patches should follow the <a href="http://patches.linuxfromscratch.org">patches format</a>. Patches for packages will be hosted on Patches project website. For example, if your hint has a patch for gcc, that patch will be hosted under gcc directory. All other patches/scripts will be available for download from the hints website.</li>
  +</ul>
  +	<p>To submit or update a hint, send an e-mail to the <a href="mailto:hints at linuxfromscratch.org">hint mailing list</a>. From there it will be picked up by the hint maintainer, who will update the hint index and the tarball. To check if your hint has already been included, you can <a href="http://linuxfromscratch.org/mailman/listinfo/hints">subscribe</a> to the hints mailinglist, check its <a href="http://linuxfromscratch.org/pipermail/hints/">archive</a> or use the <a href="../newsgroups.html">news group</a> gateway. As soon as it's added it's also viewable from the <a href="list.html">list</a> and the <a href="files/">files</a> sections on this website.</p>
  +	<p>Keep the hints list solely for <strong>submitting hints and updates to hints</strong>. If you want to discuss or announce a new hint, <a href="mailto:blfs-support at linuxfromscratch.org">blfs-support</a> is a good forum.</p>
   
   </div> <!-- end content -->
   
  @@ -68,7 +80,7 @@
   		<ul>
   		<li><a href="news.html">Hints News</a></li>
   		<li><a href="whatarehints.html" title="What are these hints for?">What are LFS hints?</a></li>
  -		<li><a href="howtowrite.html" title="Style and format of hints">How do I write LFS hints?</a></li>
  +		<li><a href="howtowrite.html" title="Style and format guidelines of hints">Write a hint</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   		<li><a href="submit.html" title="If you want to submit a new hint" class="currentpage">Submit new hint</a></li>
   		<li><a href="acknowledgements.html" title="People who earned credits for their contributions">Acknowledgements</a></li>
  
  
  
  1.20      +1 -1      www/test/hints/whatarehints.html
  
  Index: whatarehints.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/whatarehints.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- whatarehints.html	21 Aug 2003 19:15:01 -0000	1.19
  +++ whatarehints.html	25 Aug 2003 13:05:55 -0000	1.20
  @@ -67,7 +67,7 @@
   		<ul>
   		<li><a href="news.html">Hints News</a></li>
   		<li><a href="whatarehints.html" title="What are these hints for?" class="currentpage">What are LFS hints?</a></li>
  -		<li><a href="howtowrite.html" title="Style and format of hints">How do I write LFS hints?</a></li>
  +		<li><a href="howtowrite.html" title="Style and format guidelines of hints">Write a hint</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   		<li><a href="submit.html" title="If you want to submit a new hint">Submit new hint</a></li>
   		<li><a href="acknowledgements.html" title="People who earned credits for their contributions">Acknowledgements</a></li>
  
  
  
  1.33      +1 -1      www/test/lfs/packages.html
  
  Index: packages.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/lfs/packages.html,v
  retrieving revision 1.32
  retrieving revision 1.33
  diff -u -r1.32 -r1.33
  --- packages.html	21 Aug 2003 19:14:17 -0000	1.32
  +++ packages.html	25 Aug 2003 13:05:55 -0000	1.33
  @@ -44,7 +44,7 @@
   	<h2>Packages</h2>
   		<p>LFS has a list of packages which you should download. Please use the versions which are <a href="../faq/#why-not-version" title="read this if you don't intend to follow our advice">listed in the book</a>; these are tested verions which are known to work with each other. There are several ways to download the packages.</p>
   	<h3>Freshmeat</h3>
  -		<p>The first is to hunt down all the packages in <a href="view/stable/chapter04/packages.html">the book</a>. This is a laborious click-and-point process, not always succesfull since older versions of packages may become less available. In that case, <a href="http://www.google.com/">google</a> for the package (for example, <a href="http://www.google.com/search?q=bash-2.05a.tar.gz">bash-2.05a.tar.gz</a>). You can also use the sources from your Linux distribution. <a href="http://www.debian.org/">Debian</a> has an excellent <a href="http://www.debian.org/distrib/packages">search page</a> from which you can download the original sources of packages. This method is probably only useful if you really must have all the latest versions (and in that case, check out the <a href="../faq/#whynotversion">FAQ</a>).</p>
  +		<p>The first is to hunt down all the packages in <a href="view/stable/chapter04/packages.html">the book</a>. This is a laborious click-and-point process, not always succesfull since older versions of packages may become less available. In that case, <a href="http://www.google.com/">google</a> for the package (for example, <a href="http://www.google.com/search?q=bash-2.05a.tar.gz">bash-2.05a.tar.gz</a>). You can also use the sources from your Linux distribution. <a href="http://www.debian.org/">Debian</a> has an excellent <a href="http://www.debian.org/distrib/packages">search page</a> from which you can download the original sources of packages. This method is probably only useful if you really must have all the latest versions (and in that case, check out the <a href="../faq/#why-not-version">FAQ</a>).</p>
   	<h3>wget</h3>
   		<p>The second is a <a href="http://www.gnu.org/software/wget/wget.html" title="GNU wget webpage">wget</a> script. Choose between the <a href="wget/lfs-stable.wget" title="stable versions">stable</a> or the <a href="wget/lfs-cvs.wget" title="only for CVS or your own risk">CVS <em>(currently not up-to-date!)</em></a> list.  We can only guarantee that the lfs-stable.wget script is fully in sync with the stable book release. To use it, enter <code>wget -i lfs-stable.wget</code>.</p>
   	<h3>Peer-2-peer networks</h3>
  
  
  



More information about the website mailing list