El Martes, 25 de Septiembre de 2007 08:28, Chris Staub escribió:
> 1. Make and Man-DB are not in alphabetical order as they should be.
> 2. Make no longer needs Diffutils
> 3. Make uses Procps in its testsuite (specifically, the "uptime" program)
> 4. Module-init-tools needs Findutils (not just for
El Domingo, 23 de Septiembre de 2007 08:03, Chris Staub escribió:
> I just double-checked dependencies for a number of packages and have
> attached a patch with some corrections...in some cases accounting for
> changes due to newer package versions, and in others fixing mistakes in
> the existing d
El Sábado, 15 de Septiembre de 2007 22:17, Jeremy Huntwork escribió:
>
> Well, let's try this out then. If people scream we can change it back.
>
I don't care about to what list the ticket posts are send, but please, send it
to only one of them.
--
Manuel Canales Esparcia
Usuario de LFS nº2886
El Miércoles, 12 de Septiembre de 2007 19:33, Chris Staub escribió:
> Attached should be a patch to add ncurses5-config to the Ncurses program
> list, and several grammar/spelling fixes.
Applied on r8385, thanks :-)
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscra
El Viernes, 7 de Septiembre de 2007 21:18, Matthew Burgess escribió:
> Full patch series is now at
> http://www.linuxfromscratch.org/~matthew/patches/ (see the series file
> there for the order they need to be applied in).
Is there some timeline about when that patches will be applied to trunk?
El Martes, 11 de Septiembre de 2007 17:06, Dan Nicholson escribió:
>
> FYI, this is a property of xsltproc(1), and not something native to LFS.
>
Actually, it's an standard.
All XML parsers should honour XML_CATALOG_FILES, the same that all SGML
parsers should honour SGML_CATALOG_FILES
--
M
El Martes, 11 de Septiembre de 2007 16:30, Alexander E. Patrakov escribió:
> Make it easy to use a just-downloaded private copy of the correct
> version of the stylesheets.
That is already done.
You can place the stylesheets anywhere, just update the XML catalogs to point
to that path when that
El Martes, 11 de Septiembre de 2007 16:09, Alexander E. Patrakov escribió:
> Would you mind if I report this to Debian as a bug, and CC: you so that
> you get a chance to answer the replies?
If you ask about creating sepparate DB-XSL packages for each available
version, and no other Debian packa
El Martes, 11 de Septiembre de 2007 15:48, Alexander E. Patrakov escribió:
> Yes, an issue for distro package creators, but caused by LFS upstream
> not willing to cooperate :)
Hu?
What most cooperation is needed apart from saying on what external packages
version our sources depends on?
If so
El Martes, 11 de Septiembre de 2007 15:04, Alexander E. Patrakov escribió:
> The problem is that old versions of DocBook XSL are simply not available
> as Debian packages, so one cannot build-depend on them without
> immediately getting a release-critical bug report.
Forgot to mention. That's a d
El Martes, 11 de Septiembre de 2007 15:04, Alexander E. Patrakov escribió:
> OK. Now imagine the following situation: someone wants to create a
> Debian package with the LFS book. Debian policy requires that all HTML
> and PDF files are rebuilt from XML source in this case. If the LFS book
> relie
El Martes, 11 de Septiembre de 2007 08:43, Alexander E. Patrakov escribió:
> The question is how they manage to continue building packages with
> documentation successfully when DocBook XSL is upgraded. For the
> "gimp-help-2" package, the answer is that the "current" version of
> stylesheets is u
El Lunes, 10 de Septiembre de 2007 19:26, Dan Nicholson escribió:
> That would be the drawback to this approach. If we do go back to using
> the host's stylesheets, then it should be completely clear in the
> sources (or somewhere else) what version is expected. Possibly we can
> check and enforce
El Lunes, 10 de Septiembre de 2007 06:10, Randy McMurchy escribió:
> I'm wondering if we shouldn't go back to using "stock" stylesheet
> versions installed locally, and not a version included with the sources?
Looks like DB-XSL-1.73.2 is good enough to be used as the default base XSL
code for th
El Sábado, 8 de Septiembre de 2007 12:26, Matthew Burgess escribió:
> Thanks Jeremy, that was exactly the problem. I've uploaded the updated
> gcc.patch file. I just removed the '^' so the sed only matches what
> current trunk matches, rather than the ld-uClibc.so.0 entry as well which
> your '/
El Sábado, 21 de Julio de 2007 01:10, Dan Nicholson escribió:
>
> I've been playing around with jhalfs and I realized that there was no
> easy way to access the package name and version on a given page. Manuel
> and I had a discussion on alfs-discuss and he suggested using the
> and children of
El Miércoles, 5 de Septiembre de 2007 20:41, Matthew Burgess escribió:
> 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.
I will look to merge the changes into the jh-branch also. We nee
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 su
El Viernes, 31 de Agosto de 2007 15:27, sacarde escribió:
> Alle venerdì 31 agosto 2007, sacarde ha scritto:
>
> can you suggest me a way to re-initialize jhalfs in blfs step
> after a building stop in previus release ?
Please, use the alfs-discuss list for that typo of questions, thanks.
--
Man
El Miércoles, 29 de Agosto de 2007 19:15, Dan Nicholson escribió:
> Thanks. I created the directory, and you should have write privs.
>
> http://www.linuxfromscratch.org/lfs/build-logs/6.3/
>
> Please create a directory for your system with a 00-README file
> describing it like here:
>
> http://ww
El Jueves, 30 de Agosto de 2007 19:12, Dan Nicholson escribió:
> Which reminds me. Manuel, can you add man-db to the MAKEFLAGS
> blacklist for jhalfs? 2.4.4 fails pretty consistently for me on -j3.
Was added several days ago, when it start failing also to me ;-)
It's on the just-released 2.3.1 v
The jhalfs development team is pleased to announce the release of
jhalfs-2.3.1.
This is a bugs-fixes release to match LFS-6.3 and current BLFS development
book.
If you are using jhalfs-2.3, please upgrade to jhalfs-2.3.1.
The jhalfs-2.3.1 tarball can be downloaded from
http://www.linuxfromsc
El Jueves, 30 de Agosto de 2007 19:08, Jeremy Huntwork escribió:
> Because of that, I'm inclined to let the matter rest, at least for now.
> The current build method works for every default setup I've tested so
> far - I think that is good enough. At least until we encounter some more
> informatio
El Jueves, 30 de Agosto de 2007 06:33, Bruce Dubbs escribió:
> I updated all the 6.3 files on the server so the md5sums in the book now
> match the md5sums of the files. No filenames were changed.
Great, now all packages are downloaded without issues :-)
Many thanks.
--
Manuel Canales Esparcia
El Miércoles, 29 de Agosto de 2007 20:20, Bruce Dubbs escribió:
> OK, I copied the config files from development to 6.3 and renamed
> appropriately. The md5sums match what is in the book. That should fix
> the jhalfs problem.
Thanks.
I will test that the new files are properly downloaded and ve
Hi,
jhalfs has reported this when trying to build LFS-6.3:
lfs-bootscripts-6.3.tar.bz2 does not match MD5SUMS value
NEW MD5SUM: 4898129064e2edf93d52c9def3053ae1 lfs-bootscripts-6.3.tar.bz2
udev-config-6.3.tar.bz2 does not match MD5SUMS value
NEW MD5SUM: 154bb3fd0aa36506ffa57e88cc08910d udev-con
El Martes, 28 de Agosto de 2007 23:53, Dan Nicholson escribió:
> If anyone has clean test/build logs to contribute for the 6.3 book,
> please tar them up and post them with a hardware description.
> Preferably Ch. 5 and Ch. 6, but just Ch. 6 will do. They will
> eventually go here:
>
> http://www.l
El Lunes, 27 de Agosto de 2007 19:46, M.Canales.es escribió:
Actually, the solution for the book is do nothing, IMHO.
That references to the GCC and Binutils build trees has been on all *LFS-based
systems from years ago without known issues.
--
Manuel Canales Esparcia
Usuario de LFS nº2886
El Lunes, 27 de Agosto de 2007 14:17, [EMAIL PROTECTED] escribió:
> SVN-20070820
>
> When I compiled PCRE, and others, "butterfly-build" appears in the
> compiler output and harmful or not, that is unclean and unacceptable.
On a LFS or CLFS-based system, both current and old versions, there is a l
El Lunes, 20 de Agosto de 2007 07:25, Justin Robert Knierim escribió:
> For the ftp repos, I make heavy use of the wget scripts. Some are
> already rendered with the book, such as:
>
> http://www.linuxfromscratch.org/lfs/view/development/wget-list
>
> If it isn't too much trouble, could this be ad
El Miércoles, 15 de Agosto de 2007 15:07, Jeremy Huntwork escribió:
> I'm not going to push to get this into LFS. If the vast majority of
> those with a voice here are for PM in LFS, great. If not, great. :)
The question are:
What changes would be needed to let *LFS books be PM-aware? Without fo
El Lunes, 13 de Agosto de 2007 19:32, Dan Nicholson escribió:
> Yeah, that site is gone. In BLFS we're using this:
>
> http://cross-lfs.org/files/packages/svn/shadow-4.0.18.1.tar.bz2
>
> There are plenty of places we can put it on one of the LFS servers.
> downloads.linuxfromscratch.org seems like
El Lunes, 13 de Agosto de 2007 00:34, Randy McMurchy escribió:
>
> Would you recommend that we split this up a bit?
Don't should be needed. What is needed is to create a sub-routine to parse
Dbus-Bindings and Python-Modules on a different way, like was done for Xorg7.
I will try to have it done
El Miércoles, 1 de Agosto de 2007 19:43, Jeremy Huntwork escribió:
> I suppose that's argument for producing a separate set of text for 64-bit.
Not, if creating sepparate books I refuse to have separate diskusage/buildtime
blocks and entities sets for each arch.
On CLFS and HLFS that info was
El Miércoles, 1 de Agosto de 2007 00:50, Dan Nicholson escribió:
>
> I guess I just like to know how things are gonna shape up relatively.
> I.e., gcc's gonna take a while, no sense in watching the screen. I
> don't care if the numbers aren't accurate. But people using older
> hardware may be more
El Martes, 31 de Julio de 2007 16:07, Dan Nicholson escribió:
>
> http://downloads.linuxfromscratch.org/udev-config-20070731.tar.bz2
>
I think that the book URLs to download both lfs-bootscripts and udev-config
should be changed to use http://downloads.linuxfromscratch.org. It's neutral
and sho
El Lunes, 30 de Julio de 2007 21:26, Jeremy Huntwork escribió:
> I've been thinking about this some more recently. I really think it's
> not worth the time and effort (at least not now) to add the extra
> complexity to the XML/XSL to render two separate books for x86 LFS and
> x86_64 LFS. The comm
El Lunes, 30 de Julio de 2007 20:02, Bruce Dubbs escribió:
> I put out a 6.3-rc1 a week ago and there really has been very little
> feedback. Is it ready for final release?
I think so, but fixing before the missing consolelog bootscript description in
chapter07/bootscripts.xml. I have done a lot
The jhalfs development team is pleased to announce the release of jhalfs-2.3.
New features in this version:
- Many code updates to follow current SVN books
- Generation of installed files logs.
- Added an option to stop the build at a desired point
- Several bugs fixes, code clean-up and
El Viernes, 27 de Julio de 2007 02:01, Randy McMurchy escribió:
> Hi all,
>
> Best as I can tell, the Anduin package repository hasn't been updated
> for well over a month. There's probably been more than 100 package
> updates since then. I know Justin is busy these days, so should we
> just forget
El Viernes, 27 de Julio de 2007 17:36, Randy McMurchy escribió:
> Hi all,
>
> It is my pleasure to announce that Ag Hatzimanikas has accepted a
> position as a BLFS Editor. Ag brings a long time affiliation with
> the (x)LFS projects (and a great passion towards the projects), a
> great amount of L
El Jueves, 26 de Julio de 2007 18:28, Dan Nicholson escribió:
> IIRC, the last time I ran the 4.1.2 testsuite, I also had no failures.
> That wasn't during a bootstrap, though. Oh, I don't remember what
> happened with mudflap. Manuel, do you still have the test logs from
> the LFS jhalfs run you
El Miércoles, 25 de Julio de 2007 19:10, Jeremy Huntwork escribió:
> Manuel, I'm slowly beginning to understand how the HLFS render 'magic'
> works. One question: would the 'condition'
For LFS we should use the arch= attribute. It's more semantically correct.
> parameter be usable in an ENTITY
El Martes, 24 de Julio de 2007 20:12, Jeremy Huntwork escribió:
> M.Canales.es wrote:
> > I prefer to use the HLFS-way for x86_64 integration.
>
> Well, you obviously know that setup better than I do. If you could help
> me set that up, I'd appreciate it.
I have many fron
El Martes, 24 de Julio de 2007 19:51, Dan Nicholson escribió:
> Out of curiosity, will the Relax NG XML ease in generating multiple
> books from a common source?
Not, what Relax-NG make more easy is to customize the schema declaration. I.e,
to add new tags or attributes (placed on a diferent na
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 su
El Martes, 24 de Julio de 2007 17:59, Jeremy Huntwork escribió:
> My biggest problem with this approach is that it gets to be a nightmare
> to edit. But, it is do-able.
See how HLFS manages the Glibc/uClibc - Linux-2.4/2.6 books flavours and ask
Robert if it hard to maintain. Four sepparte books
El Lunes, 23 de Julio de 2007 20:49, Dan Nicholson escribió:
> That doesn't say too much. OK, looking at postix/test-vfork3.c, I
> think I see the issue. At that point it does 'unsetenv ("PATH");' and
> then tries to execute "echo". For this to work, we need to have echo
> in /bin, which we don't
El Lunes, 23 de Julio de 2007 02:37, Dan Nicholson escribió:
> That's what I meant.
tst-vfork3.out just contains:
script 1
script 1
script 1
script 1
script 1
script 2
script 2
script 2
script 2
script 2
script 3
script 3
script 3
script 3
script 3
echo failed with status 512
Do you need tst-vf
El Domingo, 22 de Julio de 2007 20:15, Dan Nicholson escribió:
>
> Do you still have the output from tst-vfork3?
>
Do you meant the log output on the posix/tst-vfork3.out file?
If the later, I will need to do a new build but stopping it before Glibc
sources and build directory deletion.
--
M
El Jueves, 19 de Julio de 2007 00:13, Matthew Burgess escribió:
> I did a full final system testsuite run with the latest package updates
> (including a repackaged version of the latest iproute2 package). No
> failures there. I've not done an ICA/farce build though, so that would
> certainly be
El Viernes, 20 de Julio de 2007 22:54, Jeremy Huntwork escribió:
> Indeed. I meant to drop something in, but forgot about it. bin86/lilo
> would probably be alright. Anyone tried grub2?
IMHO, for now lilo should be used due that the build commands could be copied
from CLFS.
For the future, see
El Viernes, 20 de Julio de 2007 22:29, George Boudreau escribió:
> Should we add lfs-x86_64 to to jhalfs now or wait a few weeks/months?
> I assume there will be a multi-lib version after all objections/ideas
> have been aired. (planning ahead for jhalfs)
Depends on how the changes are applied
El Viernes, 20 de Julio de 2007 19:22, Dan Nicholson escribió:
>
> OK, I'm going to commit that. Do you mind if I use a similar variable
> in jhalfs/LFS/lfs.xsl?
If you have commits right to the ALFS repo, fell free to do the changes.
I'm very busy now trying to install some usable host system w
El Viernes, 20 de Julio de 2007 02:08, Dan Nicholson escribió:
> Manuel,
>
> I was playing with the dump-commands output and saw a couple things that
> I thought could be cleaned up. First, I think it's nicer to create a
> global variable for newlines instead of always using the entity directly.
>
El Miércoles, 18 de Julio de 2007 02:49, Bruce Dubbs escribió:
>
> What do you want for a target release date? I would think we could get
> a -rc1 out in a week if we don't make any changes to the tool chain.
Looks good.
I will start some ICA/farce and full-testsuites builds.
--
Manuel Canale
El Martes, 17 de Julio de 2007 15:13, William Harrington escribió:
> Hello,
>
>
> Anyone have the MAKEDEV-1.8.bz2 laying around in their archives?
> I'd like to archive it. 1.7, too if it is around anywhere.
http://www.linuxfromscratch.org/~manuel/MAKEDEV-1.7.bz2
--
Manuel Canales Esparcia
U
El Viernes, 13 de Julio de 2007 18:18, Ivan Kabaivanov escribió:
> actually there's a notice just before the command you've quoted. This
> is what I'm referring to:
>
>
> If working on a platform where the name of the dynamic linker is
> something other than ld-linux.so.2, replace ld-linux.so.2
El Sábado, 14 de Julio de 2007 01:26, Dan Nicholson escribió:
>
> I would actually really like to add x86_64 (non-multilib to start)
> support to LFS and BLFS. It's becoming increasingly uncommon to even
> be able to purchase a non-64bit processor at this point. We can
> basically copy what Greg's
El Viernes, 6 de Julio de 2007 01:21, Dan Nicholson escribió:
> +ifdef V
> +Q =
> +else
> +Q = @
> +endif
> +
Yea, I saw something like that on the BusyBox makefiles the other day. Looks
good to me.
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en
Hi,
I just finished to update the LFS book sources to use the new stylesheets.
NOTE: I'm not sure if the script that generates the on-line book need be
adjusted to use the new code properly.
The Makefile has been also re-factored. There is a new "all" target and a new
ROOT_ID variable.
The R
El Jueves, 5 de Julio de 2007 15:40, Dan Nicholson escribió:
> I think this would be the best. It gives maximum flexibility if the
> stylesheets we use are local to our repos. This also solves the issue
> of people having different versions of the stylesheets installed. So
> long as someone (Manue
El Miércoles, 4 de Julio de 2007 22:59, Bruce Dubbs escribió:
>
> Do you have any insight into why there will be no 1.72.1 release?
>
Apart the comments in the commits and some developer's post in docbook-apps
saying that 1.73.0 will be released soon. I think that the main reason that
they have
El Miércoles, 4 de Julio de 2007 23:49, Matthew Burgess escribió:
> Well, I took a look at the Relax-NG stuff a while back and hit a bug in
> libxml2 (http://bugzilla.gnome.org/show_bug.cgi?id=413248). That pretty
> much stops any work on migrating the stylesheets to be Relax-NG friendly.
Actual
El Miércoles, 4 de Julio de 2007 23:29, Matthew Burgess escribió:
> I also think this is the way we should proceed. I'm not sure that we
> necessarily need to remove files that we don't require for a build of any
> of our books - in fact, keeping them around would probably make diffs
> between up
El Miércoles, 4 de Julio de 2007 22:59, Bruce Dubbs escribió:
> Manuel,
> I know that you have been working hard on the updates, but options 2
> and 3 seem to be even more work. On top of that, I suspect we will want
> to go to the next stable release when it is available, so a lot of the
> wor
Hi,
As you know, the new XSL stylesheets are ready for production time waiting the
release of stable DocBook-XSL-1.72.1.
The bad news it that there will be no DocBook-XSL-1.72.1 release, but a new
beta DocBook-XSL-1.73.0 that may contains several bugs due very intrusive
changes on how the pack
El Viernes, 8 de Junio de 2007 23:23, Dan Nicholson escribió:
> So, I think it's about time we start pushing out a 6.3 release. What
> do you guys think?
IMHO, just update to the packages listed now on Trac (except, of course, the
toolchain ones), and do package freezing to release 6.3 very soon
El Jueves, 7 de Junio de 2007 05:00, Bryan Kadzban escribió:
> this list whose address isn't resolving again. It seems like it's
> taking these messages about a half hour to get delivered. The message
> I'm replying to was sent at 21:42 EDT, but wasn't delivered to my mail
> server until 22:04 ED
El Lunes, 4 de Junio de 2007 02:45, Archaic escribió:
>
> On the vim page, where the docs are symlinked, a hardcoded reference to
> vim70 exists.
This one has been fixed in r8148. Thanks.
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en castellano:
El Jueves, 10 de Mayo de 2007 21:11, Bruce Dubbs escribió:
> Looking at the source and then running `genl -help` I get
>
> $ ./genl -help
> Usage: genl [ OPTIONS ] OBJECT | help }
> where OBJECT := { ctrl etc }
>OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] }
>
> But I have no idea wha
El Jueves, 10 de Mayo de 2007 19:56, Matthew Burgess escribió:
> Indeed, and there's no man page for it, and no useful info in --help for it
> either. I'm certainly not going to go and try to grok the source to figure
> out what on earth it does.
Looks like is related to generic netlinks control
Hi,
The LFS and BLFS stylesheets rework has been done, or as least I can't find
any obvious remaining issues.
To allow review it, the generated chunked XHTML and PDF versions for both
books can be found here:
http://www.linuxfromscratch.org/~manuel/
I will wait some days for your comments and
El Sábado, 7 de Abril de 2007 18:57, Matthew Burgess escribió:
> Thanks Greg, I'll remove the patch some time this week.
>
Matt, don't forget this one, there is no trac entry for it.
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en castellano: http
El Lunes, 9 de Abril de 2007 06:55, Jeremy Huntwork escribió:
>
> The issue was always with *outgoing* mail from mailman and a flooded
> mail queue, not a delay of accepting *incoming* mail which would have
> only happened once for each MTA.
Looks like that issue is here again :-/
--
Manuel Can
El Martes, 10 de Abril de 2007 22:02, Bruce Dubbs escribió:
>
> Looking at the output, all my issues have been addressed nicely with the
> exception of the font-family/font-style of the titles. That's not very
> important, but may be a nice tweak.
At my end there is yet an issue to be solved: le
El Martes, 10 de Abril de 2007 19:41, M.Canales.es escribió:
>
> Might be a bug in current libxml or libxslt.
>
After several versions changes and research looks that actually was a bug in
old libxslt versions that was not merging properly xsl:attribute-set settings
when the same one
El Lunes, 9 de Abril de 2007 22:50, Bruce Dubbs escribió:
> OK, I made some changes. See what you think.
In admonitions, that make all types having almost the same look. Both #E0E0E0
and #EEE are near identical.
What about this value? #DCC
On verbatim, using #EEE is like removing the border.
El Martes, 10 de Abril de 2007 19:29, Bruce Dubbs escribió:
> Mine is slightly older:
>
> $ xsltproc --version
> Using libxml 20622, libxslt 10115 and libexslt 812
> xsltproc was compiled against libxml 20622, libxslt 10115 and libexslt 812
> libxslt 10115 was compiled against libxml 20622
> libex
El Lunes, 9 de Abril de 2007 22:19, Bruce Dubbs escribió:
> [EMAIL PROTECTED]/new-xsl]$ make pdf
> xsltproc --xinclude --nonet --output ~/lfs-book/lfs-pdf.fo \
> stylesheets/lfs-pdf.xsl index.xml
> xsl:attribute-set : use-attribute-sets recursion detected
> Making portrait pages on USlette
El Domingo, 8 de Abril de 2007 23:03, Bruce Dubbs escribió:
> Manuel,
> I pulled the new style sheets from svn. How do you use them? Do you
> just have a temporary symbolic link from the trunk/BOOK/stylesheets to
> ../../branches/new-xsl/ ?
I have it in this way:
$ svn co svn+ssh://[EMAIL PRO
El Domingo, 8 de Abril de 2007 22:32, Bruce Dubbs escribió:
>
> I'll pull the xsl and look some more.
>
Great, I need inputs about the explanatory comments.
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en castellano: http://www.escomposlinux.org/l
El Domingo, 8 de Abril de 2007 21:10, Bruce Dubbs escribió:
>
> Is this a function of the reader's system or the system that renders the
> pdf. I thought the actual fonts used were enclosed in the file. I'm
> not 100% sure though.
For specifications, the Base-14 fonts must be available to all P
El Domingo, 8 de Abril de 2007 20:52, Bruce Dubbs escribió:
> One place that is still a problem is the last paragraph of 8.2 (page
> 212). The long config variables, CONFIG_NLS_DEFAULT,
> CONFIG_SMB_NLS_DEFAULT, CONFIG_FAT_DEFAULT_CODEPAGE, and
> CONFIG_FAT_DEFAULT_IOCHARSET throw off the word sp
El Domingo, 8 de Abril de 2007 19:30, Bruce Dubbs escribió:
>
> I like this a lot better.
Thanks.
> Now I'm going to get a bit picky about the pdf, but its offered in a
> constructive manner. Don't feel obligated to fix any of these issues.
> I'd like to see other opinions too.
Starting with m
El Domingo, 8 de Abril de 2007 17:33, M.Canales.es escribió:
>
> The URLs hyphenation support on the old stylesheets and FOP-0.20 was very
> ugly. I will test if the current one is more usable and, if true, trying to
> extend the support also to filenames.
And done:
http://www.lfs
El Domingo, 8 de Abril de 2007 04:28, Bruce Dubbs escribió:
Please, try to keep the CC to lfs-dev.
>
> I do think that each section in Chapters 5 and 6 that install a new
> package should start on a new page, but places like Chapters 8 and 9 and
> possibly 1, 2, 3, 4, and 7 should 'flow'.
Yes, I
Hi,
Looks like the stylesheets revision for LFS is done for now, until have
DocBook-xsl-1.72.1 available.
The unique visible change in the XHTML output is that chapters TOC has been
added, as was suggested. An on-line version is available here:
http://www.lfs-es.info/new-lfs-book/
In PDF outp
El Lunes, 2 de Abril de 2007 23:10, Jeremy Huntwork escribió:
> Does anyone see a problem with adding that dummy user/group to the
> original /etc/{passwd,group} files, perhaps with a note explaining its
> purpose? At the end of chapter 6 we would remove the user and group.
Why not to use the no
El Sábado, 31 de Marzo de 2007 03:49, Randy McMurchy escribió:
> Automating LFS has never been really a goal for me. However, it's time
> I looked into, and started using the jhalfs tool.
Great, I will be very happy to heard your feeling and complaints about the
tool when actually using it. Your
Hi,
The generation of the Index is one of the most broken parts using the new
DocBook-XSL code. That meant that that higly customized stylesheets need be
full reworked.
Due that it need be reworked in any case, I would take advantage of a new
available feature: The possibility to create separa
Hi,
A branch to develop the new XSL stylesheets has been justs created. To work
with that branch:
$ svn co svn+ssh://[EMAIL PROTECTED]/LFS/trunk/BOOK new-xsl
$ cd new-xsl/stylesheets
$ svn switch svn+ssh://[EMAIL PROTECTED]/LFS/branches/new-xsl .
>From now on, an "svn up" on the new-xsl/ dir wi
El Viernes, 23 de Marzo de 2007 22:52, Dan Nicholson escribió:
> 1. We shouldn't always point to the svn version. When a stable book is
> released, it should probably point to the stable version of the BLFS
> book. Although, there could be a time lapse where this could be a bad
> idea, i.e. LFS-6.
El Viernes, 23 de Marzo de 2007 23:24, Randy McMurchy escribió:
> Hi all,
>
> I'm ready to update the book to FOP-0.93, but wanted to throw out a
> note that we cannot use it to produce PDF output from the SVN XML
> sources.
Yes, that it a known issue. Our current stylesheets (both the DocBook-XSL
El Jueves, 22 de Marzo de 2007 19:30, Randy McMurchy escribió:
> Hi all,
>
> I'm not certain of something. Do we expect *all users* to perform the
> steps shown in the "Bash shell startup files"? I know I don't do them.
> I have my own way of setting up /etc/profile, et. all.
To me that section is
Hi,
Just for editors:
I will update tomorrow the book sources to use DocBook-XML DTD 4.5.
This is the first step (and the most simple) of the XML-tools updates planned
for this spring.
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en castellano:
El Miércoles, 21 de Marzo de 2007 19:09, Matthew Burgess escribió:
>
> Wow, sorry about that. I could have sworn I'd done that already. Anyway,
> it's done now.
Verified and confirmed that the catalog resolution works. Thanks.
Working on the commit now...
--
Manuel Canales Esparcia
Usuario d
El Miércoles, 21 de Marzo de 2007 02:05, Matthew Burgess escribió:
> Hi folks,
>
> Progress appears to being made toward a 6.3 release. We currently have 9
> tickets to resolve before we can push another release out[0].
Great :-)
> I'm happy to postpone the rendering toolchain related bugs #1947
El Martes, 20 de Marzo de 2007 06:18, Fix escribió:
> If you're building 64-bit *LFS system WITHOUT use of the cross
> compilation, you would need the 64-bit host system, I guess. That's
> what I do. And I think that system wouldn't be neither Cross nor
> Beyond LFS.
Right, but the LFS book is in
The jhalfs development team is pleased to announce the release of jhalfs-2.2.
New features in this version:
- Better support for CLFS Sysroot and CLFS Embedded books
- Support for BLFS-6.2.0
- Added customized tools support to all books
- Added blfs-tool support to all books (except CLFS
1 - 100 of 405 matches
Mail list logo