Re: [LFS Trac] #5653: alignment/blocking - LFS r12.2-107-systemd

"LFS Trac" ([email protected] via lfs-book Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.book
Message-ID <[email protected]>
#5653: alignment/blocking - LFS r12.2-107-systemd
---------------------------+-----------------------
 Reporter:  rhubarbpieguy  |       Owner:  lfs-book
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  12.4
Component:  Book           |     Version:  git
 Severity:  normal         |  Resolution:
 Keywords:                 |
---------------------------+-----------------------
Comment (by Xi Ruoyao):

 Regardless of the release managing I don't think the request is valid.
 For "mkdir build; cd build" we align it because both the parameters are
 "build".  But for this case I cannot see an relation between the
 parameters.

 So would we start to rewrite things like

 {{{
 cd ..
 cat gcc/limitx.h gcc/glimits.h gcc/limity.h > \
   `dirname $($LFS_TGT-gcc -print-libgcc-file-name)`/include/limits.h
 }}}

 to

 {{{
 cd  ..
 cat gcc/limitx.h gcc/glimits.h gcc/limity.h > \
   `dirname $($LFS_TGT-gcc -print-libgcc-file-name)`/include/limits.h
 }}}

 or

 {{{
 make install

 for target in depmod insmod modinfo modprobe rmmod; do
   ln -sfv ../bin/kmod /usr/sbin/$target
   rm -fv /usr/bin/$target
 done
 }}}

 to

 {{{
 make install

 for target in depmod insmod modinfo modprobe rmmod; do
   ln -sfv ../bin/kmod /usr/sbin/$target
   rm -fv  /usr/bin/$target
 done
 }}}

 ??? I.e. if we consider this a "different" alignment we'd have "different"
 alignments everywhere.  So "fixing" this just does not make sense to me.
-- 
Ticket URL: <https://wiki.linuxfromscratch.org/lfs/ticket/5653#comment:2>
LFS Trac <https://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.