Update of /cvsroot/leaf/doc/guide/devel-bering-uclibc
In directory sc8-pr-cvs1:/tmp/cvs-serv17959
Modified Files:
bucd-buildpacket.xml
Log Message:
Added info on new file types link and directory, documented new command-line switch
--all
Index: bucd-buildpacket.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/devel-bering-uclibc/bucd-buildpacket.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** bucd-buildpacket.xml 22 Aug 2003 17:33:08 -0000 1.1
--- bucd-buildpacket.xml 28 Aug 2003 18:03:10 -0000 1.2
***************
*** 24,27 ****
--- 24,37 ----
<revremark>Initial version</revremark>
</revision>
+
+ <revision>
+ <revnumber>0.2</revnumber>
+
+ <date>2003-08-29</date>
+
+ <authorinitials>MH</authorinitials>
+
+ <revremark>Added info on new file types link and directory, documented new
command-line switch --all</revremark>
+ </revision>
</revhistory>
</chapterinfo>
***************
*** 273,287 ****
<title>File</title>
! <para>Filename (including relative path) of the file in the package
! Source: relative (to buildtools staging-dir) path/filename to the file
! generated by buildtool. Possible file-types are:
! <itemizedlist><listitem><para>binary: (for files that are copied from
! the staging_dir of buildtool - not necessarily a
<emphasis>binary</emphasis>)</para></listitem><listitem><para>list:
! file (or pattern) to add to the packagename.list
file</para></listitem><listitem><para>conf:file
to add to packagename.conf</para></listitem><listitem><para>local: file
to add to packagename.local (for partial backups). At this point only
the type "I" (for including the file in the local backup) is
supported, type "X" (for excluding a file from the local backup)
! is not.</para></listitem></itemizedlist></para>
</section>
</section>
--- 283,317 ----
<title>File</title>
! <para>Target: filename (including relative path) that the link should
! point to (only used together with type=link)</para>
!
! <para>Filename: (including relative path) of the file in the package</para>
!
! <para>Source: relative (to buildtools staging-dir) path/filename to the
! file generated by buildtool.</para>
!
! <para>Type: specifies the how buildpacket should treat this file.
! Possible types are: <itemizedlist><listitem><para>binary: (for files
! that are copied from the staging_dir of buildtool - not necessarily a
! <emphasis>binary</emphasis>)</para></listitem><listitem><para>list: file
! (or pattern) to add to the packagename.list
file</para></listitem><listitem><para>conf:file
to add to packagename.conf</para></listitem><listitem><para>local: file
to add to packagename.local (for partial backups). At this point only
the type "I" (for including the file in the local backup) is
supported, type "X" (for excluding a file from the local backup)
! is not.</para></listitem><listitem><para>link: Specifies that this file
! is a (soft-) link that should be created during package creation.
! Filename specifies the name of the link (relative to the root dir). You
! MUST also specify Target (which tells buildpacket where the link should
! point to)</para></listitem><listitem><para>directory: Filename specifies
! the name of a directory that should be created. Source is ignored. Only
! useful if you need to create empty directories in the package (if they
! weren't empty buildpacket would create them automatically
anyway)</para></listitem></itemizedlist></para>
!
! <para>Description: only used for file type "conf" - specifies
! the description/help to be shown in the lrcfg menu</para>
!
! <para>Permissions: specifies the permissions of this file if they're
! different from the default</para>
</section>
</section>
***************
*** 291,295 ****
<para>Usage: <programlisting>buildpackage --package=packagename
--packager=name_of_packager
! [--target=packagefile] [-lrp=existing.lrp] [--verbose]</programlisting>
Example:</para>
--- 321,325 ----
<para>Usage: <programlisting>buildpackage --package=packagename
--packager=name_of_packager
! [--target=packagefile] [-lrp=existing.lrp] [-all] [--verbose]</programlisting>
Example:</para>
***************
*** 305,325 ****
<title>Options</title>
! <para><itemizedlist><listitem><para>--package The name of the package
! you compiled using <command>./buildtool.pl build
packagename</command></para></listitem><listitem><para>--packager:
The name of the user who created the package. The string you enter here
is added to the .help file (if the help section contains the
! __PACKAGER__ tag)</para></listitem><listitem><para>--target: For
! packages that create more than one lrp-file (like openssh), this
specifies which lrp to create. If this option is omitted, the value of
! --package is used</para></listitem><listitem><para>--lrp: If you already
! have an existing lrp file and you want to migrate your configuration to
! the new package, specify the lrp file here and it will be integrated
! into the package (if the .cfg file is set up correctly, the config will
! be migrated, but all binaries will be replaced with the new versions).
! This needs more work (it's pretty crude at this point), probably the
! lck-scripts by Alex Rhomberg will be integrated/used to take care of
! this.</para></listitem><listitem><para>--verbose: Turns on verbose
! logging</para></listitem></itemizedlist></para>
</section>
</section>
! </chapter>
\ No newline at end of file
--- 335,360 ----
<title>Options</title>
! <para><itemizedlist><listitem><para><command>--package</command>: The
! name of the package you compiled using <command>./buildtool.pl build
!
packagename</command></para></listitem><listitem><para><command>--packager</command>:
The name of the user who created the package. The string you enter here
is added to the .help file (if the help section contains the
! __PACKAGER__ tag)</para></listitem><listitem><para><command>--target</command>:
! For packages that create more than one lrp-file (like openssh), this
specifies which lrp to create. If this option is omitted, the value of
! --package is used</para></listitem><listitem><para><command>--lrp</command>:
! If you already have an existing lrp file and you want to migrate your
! configuration to the new package, specify the lrp file here and it will
! be integrated into the package (if the .cfg file is set up correctly,
! the config will be migrated, but all binaries will be replaced with the
! new versions). This needs more work (it's pretty crude at this
! point), probably the lck-scripts by Alex Rhomberg will be
! integrated/used to take care of
this.</para></listitem><listitem><para><command>--verbose</command>:
! Turns on verbose
logging</para></listitem><listitem><para><command>--all</command>:
! If a package definition specifies more than one package (like openssh,
! which produces ssh, sshd, sshkey and sftp), specifying
! <command>--all</command> instead of <command>--target</command> causes
! buildpacket to create all packages at
once</para></listitem></itemizedlist></para>
</section>
</section>
! </chapter>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Leaf-cvs-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits
