M.Canales.es wrote:
How that would look using "case"?
Probably something like this:
if [ -z $CONFIG ] ; then
case $i in kernel) continue ;; esac
fi
The Makefile creation take less than 5 seconds on a slow machine using any of
the jhalfs versions (the old one,
El Martes, 25 de Octubre de 2005 16:03, Jeremy Huntwork escribió:
> The idea of keeping the code cleaner by using a function is nice,
> however I disagree that this is more readable.
At least to me the version using "case" is more hard to read and isn't as
flexible as the "_IS_" function. The "
On Tue, Oct 25, 2005 at 10:03:54AM -0400, Jeremy Huntwork wrote:
>
> I'm of the opinion that leaving it at a simple case switch would have
> been the best. Does anyone else have an opinion? Does it really matter?
As for mattering, it happens what? 77? times give or take? Once before
each compil
M.Canales.es wrote:
The method implemented few minutes ago is based on that, but instead to change
all "if" to "case" a function based in "case" string text has been added and
that function is used inside the "if".
#---#
_IS_() # Function to test bu
El Lunes, 17 de Octubre de 2005 21:53, Jeremy Huntwork escribió:
> Seth W. Klein wrote:
> > case $i in *groff)
>
> Manuel, do you mind if we switch over to this method of string
> comparisons in jhalfs? David's method is nice, but the syntax Seth
> suggests is easier to read and doesn't result
> Manuel, do you mind if we switch over to this method of string
> comparisons in jhalfs? David's method is nice, but the syntax Seth
> suggests is easier to read and doesn't result in forks. Also
> it doesn't
> require a specific string format.
I'd say go with that as well. :P My method was a l
M.Canales.es wrote:
El Lunes, 17 de Octubre de 2005 22:08, M.Canales.es escribió:
after that
That should read "after all", my English sucks :-#
No worries. I understood you.
After living in NYC for several years, my Spanglish isn't so bad. :)
--
JH
--
http://linuxfromscratch.org/mailman/
El Lunes, 17 de Octubre de 2005 22:08, M.Canales.es escribió:
> after that
That should read "after all", my English sucks :-#
--
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.com
TLDP
El Lunes, 17 de Octubre de 2005 21:53, Jeremy Huntwork escribió:
> Seth W. Klein wrote:
> > case $i in *groff)
>
> Manuel, do you mind if we switch over to this method of string
> comparisons in jhalfs? David's method is nice, but the syntax Seth
> suggests is easier to read and doesn't result
Seth W. Klein wrote:
case $i in *groff)
Manuel, do you mind if we switch over to this method of string
comparisons in jhalfs? David's method is nice, but the syntax Seth
suggests is easier to read and doesn't result in forks. Also it doesn't
require a specific string format.
For examp
El Lunes, 17 de Octubre de 2005 15:06, Dan Nicholson escribió:
> I'm sure you knew this, but remember that set -e does not break for
> simple errors in while loops. Haven't looked at jhalfs to know if this
> is the case or not. Just wanted to give a heads up.
Yeah, I read the bash man page befo
M.Canales.es wrote:
2. Please don't use "&&" between commands. Reason: sometimes there's no
"&&" if the book says to do two commands in one screen/userinput block.
In order to fail reliably on any error without continuing the script,
you can add a "set -e" line just below "#!/bin/sh". This has th
Seth W. Klein wrote:
That is, in the general case, broken due to quoting. Try:
if echo "$i" | grep -q groff ; then ... ; fi
(grep -q isn't portable, either, but you may not care.)
In any case, the following is portable and fast. (Forks are expensive
and grep is never a builtin.)
cas
On Fri, Oct 14, 2005 at 09:15:24AM -0400, Jeremy Huntwork wrote:
> Alexander E. Patrakov wrote:
> >
> >[]
> >
> >if [ "$i" = "082-groff" ] ; then {do something} ; fi.
> >
> >[]
>
> Yep, I completely agree. The line above, for example, could probably read:
>
> if echo $i | grep -q "groff"
I wrote:
M.Canales.es wrote:
El Sábado, 15 de Octubre de 2005 04:54, Alexander E. Patrakov escribió:
1. For the UTF-8 book, it is also needed to download
glibc-libidn-2.3.5.tar.bz2 from lfs-matrix. Please handle this similarly
to glibc-linuxthreads and bash-doc tarballs.
This and the groff
El Sábado, 15 de Octubre de 2005 04:54, Alexander E. Patrakov escribió:
> 2. Please don't use "&&" between commands. Reason: sometimes there's no
> "&&" if the book says to do two commands in one screen/userinput block.
> In order to fail reliably on any error without continuing the script,
> you
M.Canales.es wrote:
El Sábado, 15 de Octubre de 2005 04:54, Alexander E. Patrakov escribió:
1. For the UTF-8 book, it is also needed to download
glibc-libidn-2.3.5.tar.bz2 from lfs-matrix. Please handle this similarly
to glibc-linuxthreads and bash-doc tarballs.
This and the groff-patchlevel
El Sábado, 15 de Octubre de 2005 04:54, Alexander E. Patrakov escribió:
> 1. For the UTF-8 book, it is also needed to download
> glibc-libidn-2.3.5.tar.bz2 from lfs-matrix. Please handle this similarly
> to glibc-linuxthreads and bash-doc tarballs.
This and the groff-patchlevel issue should both
El Sábado, 15 de Octubre de 2005 04:54, Alexander E. Patrakov escribió:
> Two more feature requests.
>
> 1. For the UTF-8 book, it is also needed to download
> glibc-libidn-2.3.5.tar.bz2 from lfs-matrix. Please handle this similarly
> to glibc-linuxthreads and bash-doc tarballs.
Working on it.
El Sábado, 15 de Octubre de 2005 04:42, Alexander E. Patrakov escribió:
> The problem is only with non-LFS hosts that define
> NONINTERACTIVE_LOGIN_SHELLS. Since the "lfs" user never logs in using an
> interactive shell, his .bash_profile is never used on "normal" hosts and
> (as already mentioned
Alexander E. Patrakov wrote:
> The problem is only with non-LFS hosts that define
> NONINTERACTIVE_LOGIN_SHELLS. Since the "lfs" user never logs in using an
> interactive shell, his .bash_profile is never used on "normal" hosts and
> (as already mentioned) only causes damage on "strange" hosts.
M.Canales.es wrote:
Hi!
I'm very happy to announce that jhalfs is now able to build a full LFS SVN
system (or any other LFS XML sources based in current LFS SVN) in a very
simple way and using the actual commands found in the XML sources.
The sources can be downloaded via
svn co svn://svn.l
Jeremy Huntwork wrote:
Alexander E. Patrakov wrote:
Jeremy Huntwork wrote:
BTW, has anyone else tried this?
The showstopper is in /home/lfs/.bash_profile: the "su" command starts
a shell that, as a result, waits for user input. I deleted that file.
Hrm. I'm not seeing the behavior you'
El Viernes, 14 de Octubre de 2005 17:08, Bruce Dubbs escribió:
> /etc/fstab is a different matter. If jhalfs could pick up a custom file
> from the host system written before running, it might avoid a
> post-script edit.
Added a switch to can submit a real /etc/fstab file, and a note on the fina
> Fixed but using something a little diferent:
>
> if [ ${i:4:8} = "binutils" ] ; then
>
> That will match both 027-binutils-pass1 and 036-binutils-pass2 ;-)
True true... Hopefully the schema doesn't change dramatically on us. :)
Looks good, though. :) Handy little thing to know for a substr
El Viernes, 14 de Octubre de 2005 20:17, David Fix escribió:
>
> if [ ${i: -5} = "groff" ] ; then {do something} ; fi
Fixed but using something a little diferent:
if [ ${i:4:8} = "binutils" ] ; then
That will match both 027-binutils-pass1 and 036-binutils-pass2 ;-)
--
Manuel Cana
[EMAIL PROTECTED] wrote:
> El Viernes, 14 de Octubre de 2005 19:52, David Fix escribió:
>
>> You bet. :) Just remember to change the -5 to whatever the length
>> of the command is that you're checking against. :)
>
> The number means the lenght of the string after the - right?
Correct... The
El Viernes, 14 de Octubre de 2005 19:52, David Fix escribió:
> You bet. :) Just remember to change the -5 to whatever the length of the
> command is that you're checking against. :)
The number means the lenght of the string after the - right?
--
Manuel Canales Esparcia
Usuario de LFS nº2886:
El Viernes, 14 de Octubre de 2005 17:08, Bruce Dubbs escribió:
> I havn't tried jhalfs yet, but as a suggestion, /etc/shadow could have a
> null root password:
>
> echo "root" > /etc/shadow
Yes, but that will implies another deviation from the book's commands, and not
to corfim that Shad
[EMAIL PROTECTED] wrote:
> El Viernes, 14 de Octubre de 2005 15:36, David Fix escribió:
>
>> Sorry, a bit of a typo, but this is "more" correct:
>>
>> if [ ${i: -5} = "groff" ] ; then {do something} ; fi
>>
>
> That sounds good and is more portable for when supporting Cross-LFS.
>
> I will tes
El Viernes, 14 de Octubre de 2005 16:19, Alexander E. Patrakov escribió:
> Jeremy Huntwork wrote:
> > BTW, has anyone else tried this?
>
> The showstopper is in /home/lfs/.bash_profile: the "su" command starts a
> shell that, as a result, waits for user input. I deleted that file.
/home/lfs/.bash
El Viernes, 14 de Octubre de 2005 15:36, David Fix escribió:
> Sorry, a bit of a typo, but this is "more" correct:
>
> if [ ${i: -5} = "groff" ] ; then {do something} ; fi
>
That sounds good and is more portable for when supporting Cross-LFS.
I will test it soon, many thanks :-)
--
Manuel Cana
Jeremy Huntwork wrote:
> M.Canales.es wrote:
>
>> Hi!
>>
>> I'm very happy to announce that jhalfs is now able to build a full LFS
>> SVN system (or any other LFS XML sources based in current LFS SVN) in
>> a very simple way and using the actual commands found in the XML sources.
>
>
> BTW, has
Alexander E. Patrakov wrote:
Jeremy Huntwork wrote:
BTW, has anyone else tried this?
The showstopper is in /home/lfs/.bash_profile: the "su" command starts a
shell that, as a result, waits for user input. I deleted that file.
Hrm. I'm not seeing the behavior you're describing. jhalfs buil
Jeremy Huntwork wrote:
BTW, has anyone else tried this?
The showstopper is in /home/lfs/.bash_profile: the "su" command starts a
shell that, as a result, waits for user input. I deleted that file.
Can't test any further because of problems with electrical power (aka
brownout) in the house.
M.Canales.es wrote:
Hi!
I'm very happy to announce that jhalfs is now able to build a full LFS SVN
system (or any other LFS XML sources based in current LFS SVN) in a very
simple way and using the actual commands found in the XML sources.
BTW, has anyone else tried this? Any other suggestion
> I'd suggest something like this:
>
> if [ ${string: -5} = "groff" ] ; then {do something} ; fi
>
> Dave :)
Sorry, a bit of a typo, but this is "more" correct:
if [ ${i: -5} = "groff" ] ; then {do something} ; fi
Close, but had the wrong variable. :P
Dave
--
http://linuxfro
[EMAIL PROTECTED] wrote:
> Alexander E. Patrakov wrote:
>> Feature request: don't hardcode target numbers. E.g., in my UTF-8
>> book, a new package (gdbm) has been added, thus causing number skew
>> for all packages after it. Thus, constructions of the following form
>> fail:
>>
>> if [ "$i" = "0
Alexander E. Patrakov wrote:
Feature request: don't hardcode target numbers. E.g., in my UTF-8 book,
a new package (gdbm) has been added, thus causing number skew for all
packages after it. Thus, constructions of the following form fail:
if [ "$i" = "082-groff" ] ; then {do something} ; fi.
U
M.Canales.es wrote:
Hi!
I'm very happy to announce that jhalfs is now able to build a full LFS SVN
system (or any other LFS XML sources based in current LFS SVN) in a very
simple way and using the actual commands found in the XML sources.
The sources can be downloaded via
svn co svn://svn.l
> Is this an alternative to alfs or something more different [sorry about
> the English there - yeuckkk!] than that?
>
> Is it suitable for "non" LFS Developers?
Hi Alan,
I put together something a bit back to automate installation of other
applications. You'd need to write profiles for it for LF
El Miércoles, 12 de Octubre de 2005 14:06, Alan Lord escribió:
> Is this an alternative to alfs or something more different [sorry about
> the English there - yeuckkk!] than that?
Is something very different to nALFS. nALFS have many features and uses beyond
the build of a base LFS system.
> Is
Manuel Wrote:
>Hi!
>
>I'm very happy to announce that jhalfs is now able to build a full LFS
SVN
>system (or any other LFS XML sources based in current LFS SVN) in a
very
>simple way and using the actual commands found in the XML sources.
>The sources can be downloaded via
>svn co svn://svn.li
Hi!
I'm very happy to announce that jhalfs is now able to build a full LFS SVN
system (or any other LFS XML sources based in current LFS SVN) in a very
simple way and using the actual commands found in the XML sources.
The sources can be downloaded via
svn co svn://svn.linuxfromscratch.org/ALF
44 matches
Mail list logo
