Re: [PATCH] Add screen install attributes for final system packages
El Sábado, 21 de Julio de 2007 01:42, Dan Nicholson escribió: Another jhalfs helper. As has been discussed before, it would be nice to mark the screen sections with an attribute to announce that it will be installing to the system rather than just working in the source/build tree. Manuel suggested adding the attribute userlevel=install, so I've done that for the Ch. 6 packages and the kernel in Ch. 8. Now that LFS-6.3 has been released and we are just openning a new 7.0 milestone, I think that is the best momment to implement that XML additions, if they are accepted. For reference, the propossals was made on this posts: http://linuxfromscratch.org/pipermail/lfs-dev/2007-July/059682.html http://linuxfromscratch.org/pipermail/lfs-dev/2007-July/059687.html If there is no objetions about that additions, I will commit the changes this weekend. Comments, complaints? -- Manuel Canales Esparcia Usuario de LFS nº2886: http://www.linuxfromscratch.org LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info TLDP-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [PATCH] Add screen install attributes for final system packages
On Wed, 5 Sep 2007 19:52:41 +0200, M.Canales.es [EMAIL PROTECTED] wrote: http://linuxfromscratch.org/pipermail/lfs-dev/2007-July/059682.html http://linuxfromscratch.org/pipermail/lfs-dev/2007-July/059687.html If there is no objetions about that additions, I will commit the changes this weekend. Comments, complaints? No comments or complaints here. We might hit merge problems between this and the jh-branch merge, but they'll be pretty trivial to fix up, I should think. Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [PATCH] Add screen install attributes for final system packages
On Wed, Sep 05, 2007 at 07:52:41PM +0200, M.Canales.es wrote: If there is no objetions about that additions, I will commit the changes this weekend. +1 Comments, complaints? Currently, my biggest complaint is that I have no ice cream. :( -- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [PATCH] Add screen install attributes for final system packages
El Sábado, 21 de Julio de 2007 01:42, Dan Nicholson escribió: Another jhalfs helper. As has been discussed before, it would be nice to mark the screen sections with an attribute to announce that it will be installing to the system rather than just working in the source/build tree. Manuel suggested adding the attribute userlevel=install, so I've done that for the Ch. 6 packages and the kernel in Ch. 8. IMHO, both this and the sect1info patch are good additions for the 7.x milestone. But I think also that could be better to apply they after the final 6.3 release to can do more easy merges from/to the 6.3 branch to/from trunk. -- Manuel Canales Esparcia Usuario de LFS nº2886: http://www.linuxfromscratch.org LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info TLDP-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
[PATCH] Add screen install attributes for final system packages
Another jhalfs helper. As has been discussed before, it would be nice to
mark the screen sections with an attribute to announce that it will be
installing to the system rather than just working in the source/build
tree. Manuel suggested adding the attribute userlevel=install, so I've
done that for the Ch. 6 packages and the kernel in Ch. 8.
This allows a really simple stylesheet to be created so that interesting
things can be done. For instance, I created a paco stylesheet to wrap the
install commands like so:
paco -lp+ ${package}-${version}
make install
Combined with the previous patch to export the package name and version
number, LFS is practically ready for a package manager and it required
no additional hacks.
Any objections? Again, there was no diff in the HTML. There might still
be interest in deciding what are install actions and what aren't, but
that's a separate discussion.
--
Dan
BOOK/chapter06/autoconf.xml |2 +-
BOOK/chapter06/automake.xml |2 +-
BOOK/chapter06/bash.xml |2 +-
BOOK/chapter06/binutils.xml |4 ++--
BOOK/chapter06/bison.xml |2 +-
BOOK/chapter06/bzip2.xml |4 ++--
BOOK/chapter06/coreutils.xml |6 +++---
BOOK/chapter06/db.xml|4 ++--
BOOK/chapter06/diffutils.xml |2 +-
BOOK/chapter06/e2fsprogs.xml |4 ++--
BOOK/chapter06/file.xml |2 +-
BOOK/chapter06/findutils.xml |4 ++--
BOOK/chapter06/flex.xml |6 +++---
BOOK/chapter06/gawk.xml |2 +-
BOOK/chapter06/gcc.xml |6 +++---
BOOK/chapter06/gettext.xml |2 +-
BOOK/chapter06/glibc.xml | 14 +++---
BOOK/chapter06/grep.xml |2 +-
BOOK/chapter06/groff.xml |4 ++--
BOOK/chapter06/grub.xml |2 +-
BOOK/chapter06/gzip.xml |4 ++--
BOOK/chapter06/iana-etc.xml |2 +-
BOOK/chapter06/inetutils.xml |4 ++--
BOOK/chapter06/iproute2.xml |4 ++--
BOOK/chapter06/kbd.xml |4 ++--
BOOK/chapter06/less.xml |2 +-
BOOK/chapter06/libtool.xml |2 +-
BOOK/chapter06/linux-headers.xml |2 +-
BOOK/chapter06/m4.xml|2 +-
BOOK/chapter06/make.xml |2 +-
BOOK/chapter06/man-db.xml|4 ++--
BOOK/chapter06/man-pages.xml |2 +-
BOOK/chapter06/mktemp.xml|2 +-
BOOK/chapter06/module-init-tools.xml |2 +-
BOOK/chapter06/ncurses.xml | 14 +++---
BOOK/chapter06/patch.xml |2 +-
BOOK/chapter06/perl.xml |2 +-
BOOK/chapter06/procps.xml|2 +-
BOOK/chapter06/psmisc.xml|6 +++---
BOOK/chapter06/readline.xml |6 +++---
BOOK/chapter06/sed.xml |2 +-
BOOK/chapter06/shadow.xml|8
BOOK/chapter06/sysklogd.xml |4 ++--
BOOK/chapter06/sysvinit.xml |4 ++--
BOOK/chapter06/tar.xml |2 +-
BOOK/chapter06/texinfo.xml |4 ++--
BOOK/chapter06/udev.xml | 12 ++--
BOOK/chapter06/util-linux.xml|2 +-
BOOK/chapter06/vim.xml |8
BOOK/chapter06/zlib.xml |8
BOOK/chapter08/kernel.xml| 10 +-
BOOK/stylesheets/dump-commands.xsl |2 +-
52 files changed, 106 insertions(+), 106 deletions(-)
diff --git a/BOOK/chapter06/autoconf.xml b/BOOK/chapter06/autoconf.xml
index b85fd8b..fb4d980 100644
--- a/BOOK/chapter06/autoconf.xml
+++ b/BOOK/chapter06/autoconf.xml
@@ -56,7 +56,7 @@
paraInstall the package:/para
-screenuserinputmake install/userinput/screen
+screen userlevel=installuserinputmake install/userinput/screen
/sect2
diff --git a/BOOK/chapter06/automake.xml b/BOOK/chapter06/automake.xml
index 2ede092..6204a59 100644
--- a/BOOK/chapter06/automake.xml
+++ b/BOOK/chapter06/automake.xml
@@ -54,7 +54,7 @@
paraInstall the package:/para
-screenuserinputmake install/userinput/screen
+screen userlevel=installuserinputmake install/userinput/screen
/sect2
diff --git a/BOOK/chapter06/bash.xml b/BOOK/chapter06/bash.xml
index e9b69e9..721029b 100644
--- a/BOOK/chapter06/bash.xml
+++ b/BOOK/chapter06/bash.xml
@@ -92,7 +92,7 @@ chown -Rv nobody .//userinput/screen
paraInstall the package:/para
-screenuserinputmake install/userinput/screen
+screen userlevel=installuserinputmake install/userinput/screen
paraRun the newly compiled commandbash/command program (replacing
the one that is
currently being executed):/para
diff --git a/BOOK/chapter06/binutils.xml b/BOOK/chapter06/binutils.xml
index bc86ff3..3925219 100644
--- a/BOOK/chapter06/binutils.xml
+++ b/BOOK/chapter06/binutils.xml
@@ -103,12 +103,12 @@ cd ../binutils-build/userinput/screen
Re: [PATCH] Add screen install attributes for final system packages
Dan Nicholson wrote:
Another jhalfs helper. As has been discussed before, it would be nice to
mark the screen sections with an attribute to announce that it will be
installing to the system rather than just working in the source/build
tree. Manuel suggested adding the attribute userlevel=install, so I've
done that for the Ch. 6 packages and the kernel in Ch. 8.
This allows a really simple stylesheet to be created so that interesting
things can be done. For instance, I created a paco stylesheet to wrap the
install commands like so:
paco -lp+ ${package}-${version}
make install
Combined with the previous patch to export the package name and version
number, LFS is practically ready for a package manager and it required
no additional hacks.
Any objections? Again, there was no diff in the HTML. There might still
be interest in deciding what are install actions and what aren't, but
that's a separate discussion.
These additions are benign and will have no impact on older versions
of jhalfs (2.2 or less). During the last quarter of 2006 similar changes
were discussed for jhalfs-3.0 but it died from lack of interest.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
