cvs commit: ALFS syntax.txt

highos at linuxfromscratch.org highos at linuxfromscratch.org
Fri Apr 19 08:17:31 PDT 2002


highos      02/04/19 08:17:31

  Modified:    .        syntax.txt
  Log:
  Here we go.. getting there ;)
  
  I re-read/skimmed the last month of alfs-discuss while writting this part
  up.  So i've tried to take everyone's opinion on the best syntax when I
  wrote this.  I know many will speak up when this get's checked in a few
  sec, please do.. i always enjoy the comments.  And this isn't "set in
  stone", not yet.
  
  But it will be.  Fairly soon, for 1.0.  I know i'm not the only one that's
  getting sick and tired of talking about this syntax over and over again *g*
  
  Revision  Changes    Path
  1.3       +132 -20   ALFS/syntax.txt
  
  Index: syntax.txt
  ===================================================================
  RCS file: /home/cvsroot/ALFS/syntax.txt,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- syntax.txt	27 Mar 2002 17:52:24 -0000	1.2
  +++ syntax.txt	19 Apr 2002 15:17:31 -0000	1.3
  @@ -1,27 +1,138 @@
  -Proposed "official" syntax for ALFS:
  -====================================
  +Proposed official syntax for ALFS:
  +==================================
   
  -This will have todo untill better docs can be written.
  +    o This will shortly be moved into Docbook XML for the ALFS 1.0 rleease,
  +      untill then, this will have todo ;)
   
  -In the mean time, we can at least build up a reference
  -of the current plans for the syntax.
  +    o We could perhaps move <command /> to an attribute.
  +      Not sure how much of a good idea that is however.
   
  +    o Using <parameter/> instead of <option /> for configure/make/execute.
  +      Needs more though.  Id prefer to <option /> stays with configure and
  +      friends then just moving over to copy and friends.  Perhaps we can find
  +      another name for them instead.. or just leave it as-is and say stfu ;)
   
  -Generic Tags:
  --------------
  -
  -unpack
  -configure
  -make
  -execute
  -remove
  -copy
  -move
  -link
  -mkdir
  -permissions
  -setenv
  +    o Because the usage of soft links (symbolic) are so popular, we _strongly_
  +      suggest that anyone writting an ALFS implementation leave them as
  +      default.  One less thing for profile writters having to keep track of.
   
  +      We could problably set it as a default with a DTD, but i doubt all
  +      implementations will even follow a DTD, so i just want to mention that
  +      here.
  +
  +
  +Configure:
  +----------
  +
  +    <configure base="">
  +	<command />
  +        <option />
  +    </configure>
  +
  +eg;
  +
  +    <configure base="/tmp/sed-3.02">
  +	<option>--prefix=/tmp/sed</option>
  +    </configure>
  +
  +
  +Make:
  +-----
  +
  +    <make base="">
  +	<option />
  +    </make>
  +
  +eg;
  +
  +    <make base="/tmp/sed-3.02">
  +	<option>install</option>
  +    </make>
  +
  +
  +Execute:
  +--------
  +
  +    <execute base="">
  +	<command />
  +        <option />
  +    </execute>
  +
  +eg;
  +
  +    <execute base="/tmp">
  +	<command>touch</command>
  +	<option>foobar.txt</option>
  +    </execute>
  +
  +
  +Mkdir:
  +------
  +
  +    <mkdir base="">
  +	<option />
  +        <name />
  +    </mkdir>
  +
  +eg;
  +
  +    <mkdir base="/tmp">
  +	<name>foo</name>
  +	<name>bar</name>
  +    </mkdir>
  +
  +
  +Copy:
  +-----
  +
  +    <copy base="">
  +	<option />
  +        <source />
  +	<destination />
  +    </copy>
  +
  +eg;
  +
  +    <copy base="/tmp">
  +	<source>foo</source>
  +	<destination>bar</destination>
  +    </copy>
  +
  +
  +Move:
  +-----
  +
  +    <move base="">
  +	<option />
  +        <source />
  +	<destination />
  +    </move>
  +
  +eg;
  +
  +    <move base="/tmp">
  +	<source>foo</source>
  +	<destination>bar</destination>
  +    </move>
  +
  +
  +Link:
  +-----
  +
  +    <link type="soft|hard" base="">
  +	<source />
  +        <destination />
  +    </link>
  +
  +eg;
  +
  +    <link base="/tmp">
  +	<source>foo</source>
  +	<destination>bar</destination>
  +    </link>
  +
  +
  +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   Generic Package:
   ----------------
  @@ -38,7 +149,8 @@
   
   I've presently left out the prebuild/build/postbuild (setup/build/install)
   untill we pick the best way to deal this this.  Allthough it would problably
  -be best to leave the use of them optional anyways. (ala target problably)
  +be best to leave the use of them optional anyways. (ala stage problably)
  +
   
   Generic Profile:
   ----------------
  
  
  
-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe alfs-discuss' in the subject header of the message



More information about the alfs-discuss mailing list