Re: r7105 - in trunk/BOOK/stylesheets/lfs-xsl/docbook-xsl-snapshot
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 the next months (maybe the next upgrade will be to DB-5 + DB-XSL-NS-1.74.1, but that is another beast), that is wy I updated the code to that release instead to the most current snapshot code. About going again to system-side installed DB-XSL version, is a matter to update the version and instrucctions in the BLFS page, and to install DB-XSL-1.73.2 on all servers that are rendering *LFS books, i.e., quantum, andiun, and the CLFS servers. CC to lfs-dev and clfs-dev to let editor and servers admins opine about this. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: docbook-xsl-1.71.1 + xmlto +dbus-build: failure
El Miércoles, 22 de Agosto de 2007 18:29, M.Canales.es escribió: On a related topic, docbook-xsl-1.73.1 was released 19-08-2007, just few hours after the book was updated to docbook-xsl-1.71.1 :-/ Note: docbook-xsl-1.73.1 is very buggy. A new docbook-xsl-1.73.2 version will be released soon. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Additional wget-list renders
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 added for blfs and hlfs as well? The command is the same, make wget-list with whatever BASEDIR you need. If it is too much a pain, I can keep rendering them manually on quandary (my server) instead. Updated the Makefile for both, HLFS and BLFS. If the server is using that Makefile to render the books (I think so), its wget-list files should be available on-line at the next render. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Akode and FFmpeg
El Miércoles, 15 de Agosto de 2007 00:18, Randy McMurchy escribió: I thought about this today as well. And if Bruce doesn't have the time to update, I've already installed and logged about 1/3 of the KDE packages, so it wouldn't be hard to update. I'd like get it done one way or the other before we release BLFS-6.3. When updating KDE to 3.5.7, take note that there are several security patches, at this moment there is 3 for KDE packages and one for Koffice: ftp://ftp.kde.org/pub/kde/security_patches -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Missing upstream Mplayer-1.0rc1 patch?
Hi, In the Mplayer homepage, at the end of the paragraph about the solution for the stack overflow in stream_cdd.c, there is this note: If you decide to stay with rc1, don't forget to also apply this older fix (http://www.mplayerhq.hu/MPlayer/patches/asmrules_fix_20061231.diff) But that patch is not in our Mplayer page. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Missing upstream Mplayer-1.0rc1 patch?
El Jueves, 16 de Agosto de 2007 22:33, Randy McMurchy escribió: Good catch, Manuel. I completely overlooked that. You wanna throw it on the MPlayer page, or do you want me to do it? If you say me the proper configure options to build against installed FFmpeg, I will build now Mplayer with that patch applied and test how it work with good videos and broken videos. If all go well, I can do the update. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Missing upstream Mplayer-1.0rc1 patch?
El Jueves, 16 de Agosto de 2007 22:44, Randy McMurchy escribió: Here's the entire configure command I used (the parms for FFmpeg are below this): Thanks :-) -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Akode and FFmpeg
Hi, Trying to build KDE I noticed that akode-2.0.1 in not available upstream, current version is akode-2.0.2. And there is no akode-2.0.1 packages on anduin nor other mirrors. Thus we need to update akode to 2.0.2 (there is also KDE-3.5.7 availble but no open ticket yet) or change the dowload link for 2.0.1 version to one of the URLs that can be found via http://www.filewatcher.com/ Akode includes an experimental FFmpeg codec support that in akode-2.0.1 is not enabled by default, but in akode-2.0.2 it is enabled if FFmpeg is found, but it fail to build against the current FFmpeg version in BLFS with: Making all in ffmpeg_decoder make[5]: Entering directory `/home/macana/paquetes/kdemultimedia/akode-2.0.2/akode/plugins/ffmpeg_decoder' if /bin/sh ../../../libtool --silent --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../akode/lib -I../../../akode/lib -I../../../akode/lib -I/usr/include/ffmpeg -I/usr/include/ffmpeg -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -MT ffmpeg_decoder.lo -MD -MP -MF .deps/ffmpeg_decoder.Tpo -c -o ffmpeg_decoder.lo ffmpeg_decoder.cpp; \ then mv -f .deps/ffmpeg_decoder.Tpo .deps/ffmpeg_decoder.Plo; else rm -f .deps/ffmpeg_decoder.Tpo; exit 1; fi ffmpeg_decoder.cpp: In member function 'virtual bool aKode::FFMPEGDecoder::openFile()': ffmpeg_decoder.cpp:202: warning: comparison between signed and unsigned integer expressions ffmpeg_decoder.cpp: In member function 'virtual bool aKode::FFMPEGDecoder::readFrame(aKode::AudioFrame*)': ffmpeg_decoder.cpp:317: warning: 'avcodec_decode_audio' is deprecated (declared at /usr/include/ffmpeg/avcodec.h:2803) ffmpeg_decoder.cpp:319: warning: 'avcodec_decode_audio' is deprecated (declared at /usr/include/ffmpeg/avcodec.h:2803) /bin/sh ../../../libtool --silent --tag=CXX --mode=link g++ -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common-o libakode_ffmpeg_decoder.la -rpath /opt/kde-3.5.6/lib -avoid-version -no-undefined -Wl,--no-undefined -Wl,--allow-shlib-undefined ffmpeg_decoder.lo ../../lib/libakode.la -lavcodec -lz -la52 -lmp3lame -lm -ldl -lX11 -lXext -lavutil -lavformat -lavcodec -lz -la52 -lmp3lame -lm -ldl -lX11 -lXext -lavutil .libs/ffmpeg_decoder.o: In function `aKode::FFMPEGDecoder::seek(long)': ffmpeg_decoder.cpp:(.text+0x39a): undefined reference to `av_seek_frame(AVFormatContext*, int, long long, int)' .libs/ffmpeg_decoder.o: In function `aKode::FFMPEGDecoder::FFMPEGDecoder(aKode::File*)': ffmpeg_decoder.cpp:(.text+0x45c): undefined reference to `av_register_all()' .libs/ffmpeg_decoder.o: In function `aKode::FFMPEGDecoder::FFMPEGDecoder(aKode::File*)': ffmpeg_decoder.cpp:(.text+0x50c): undefined reference to `av_register_all()' .libs/ffmpeg_decoder.o: In function `aKode::FFMPEGDecoder::closeFile()': ffmpeg_decoder.cpp:(.text+0x584): undefined reference to `avcodec_close(AVCodecContext*)' ffmpeg_decoder.cpp:(.text+0x5a3): undefined reference to `av_close_input_file(AVFormatContext*)' .libs/ffmpeg_decoder.o: In function `aKode::FFMPEGDecoder::openFile()': ffmpeg_decoder.cpp:(.text+0x657): undefined reference to `init_put_byte(ByteIOContext*, unsigned char*, int, int, void*, int (*) (void*, unsigned char*, int), int (*)(void*, unsigned char*, int), long long (*)(void*, long long, int))' ffmpeg_decoder.cpp:(.text+0x6ae): undefined reference to `get_buffer(ByteIOContext*, unsigned char*, int)' ffmpeg_decoder.cpp:(.text+0x6c8): undefined reference to `av_probe_input_format(AVProbeData*, int)' ffmpeg_decoder.cpp:(.text+0x720): undefined reference to `av_open_input_stream(AVFormatContext**, ByteIOContext*, char const*, AVInputFormat*, AVFormatParameters*)' ffmpeg_decoder.cpp:(.text+0x735): undefined reference to `av_find_stream_info(AVFormatContext*)' ffmpeg_decoder.cpp:(.text+0x8dd): undefined reference to `avcodec_find_decoder(CodecID)' ffmpeg_decoder.cpp:(.text+0x906): undefined reference to `avcodec_open(AVCodecContext*, AVCodec*)' .libs/ffmpeg_decoder.o: In function `aKode::FFMPEGDecoder::readPacket()': ffmpeg_decoder.cpp:(.text+0xada): undefined reference to `av_init_packet(AVPacket*)' ffmpeg_decoder.cpp:(.text+0xaee): undefined reference to `av_read_frame(AVFormatContext*, AVPacket*)' .libs/ffmpeg_decoder.o: In function `aKode::FFMPEGDecoder::readFrame(aKode::AudioFrame*)': ffmpeg_decoder.cpp:(.text+0xbe8): undefined reference to `avcodec_decode_audio(AVCodecContext*, short*, int*, unsigned char*, int)' collect2: ld returned 1 exit status make[5]: *** [libakode_ffmpeg_decoder.la] Error 1 To can build akode-2.0.2 having FFmpeg installed I
Re: RP-PPPoE
El Miércoles, 15 de Agosto de 2007 00:37, Randy McMurchy escribió: My current installation it is /usr/bin/logger ?? (not sure what to think about it, Dave) Now the LFS-Bootscripts don't use logger, thus logger is not moved anymore to /bin in the LFS book. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Akode and FFmpeg
El Miércoles, 15 de Agosto de 2007 00:43, Dan Nicholson escribió: Well, it looks like it's trying to get the linker to not barf on undefined symbols with -Wl,--allow-shlib-undefined, but maybe I don't understand that option correctly. Anyway, in my ffmpeg from 20070128, libavformat has av_seek_frame, and it looks like ffmpeg_decoder.o is getting linked with -lavformat. Maybe you can check on yours. $ nm /usr/lib/libavformat.so | grep av_seek_frame nm: /usr/lib/libavformat.so: no symbols I have build a lot of packages, but until now I have not tested they except X and the Nvidia module. Waiting to finish KDE build to start finding what is broken ... -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Akode and FFmpeg
El Miércoles, 15 de Agosto de 2007 01:29, Randy McMurchy escribió: Dan Nicholson wrote these words on 08/14/07 18:19 CST: $ readelf -s /usr/lib/libavformat.so | grep av_seek_frame [EMAIL PROTECTED]: ~ readelf -s /usr/lib/libavformat.so | grep av_seek_frame 112: 0001e520 1670 FUNCGLOBAL DEFAULT 10 av_seek_frame_binary 132: 0001fe30 1885 FUNCGLOBAL DEFAULT 10 av_seek_frame The same here, but in different address. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Gnome-Python
El Domingo, 12 de Agosto de 2007 18:36, Dan Nicholson escribió: And by couple of hours, I meant 15 :) Anyway, it's in there now at r7047. The text is still quite lacking, but I believe the stats and dependencies are accurate. I don't know if the dependencies are accurate or not, but to can build all listed modules other 108 packages need be build. And that following only the required and recommended dependencies. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Gnome-Python
El Domingo, 12 de Agosto de 2007 20:29, Dan Nicholson escribió: I realize that this is gonna hurt in jhalfs :) If you have any suggestions on how to break things up a bit, let me know. Yeah, I'm trying yet to depure all that circular dependencies when optional ones are selected (Gnome-Python-Desktop is a very bad beast). Don't worry about blfs-tool, it's just a helper to track dependencies, to read the book in a almost linear way, and to create base build scripts that might or might not work. It's not for newies and is hard to use by desing ;-) -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Gnome-Python
El Domingo, 12 de Agosto de 2007 23:45, Randy McMurchy escribió: That is incredible. No telling how many more if you install the optional ones. Can your tool provide a total? It would be interesting. And it sure was a PIA to build because of all those dependencies. With all optional dependencies enabled the total is 205 packages :-0 Actually almost all of them are to build Gnome-Python and Gnome-Python-Desktop modules. The other modules have few dependencies. But due that all modules are in the same page, blfs-tool generates the full tree incuded when the user only need PyXML or Pycairo. Fun, fun... -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: tcl test suite
El Lunes, 6 de Agosto de 2007 20:34, Randy McMurchy escribió: [EMAIL PROTECTED] wrote these words on 08/06/07 03:59 CST: The tcl section mentions that the test suit should be run by issuing make test. However, I've found that with that, the clock test will always fail. I wonder what is causing that? I can not reproduce the failure, and the test completes without issue every time. A question, do you have (dragosi and Randy) set TZ on our default environment? Maybe the issue is that the test only fails when TZ is (un)set in the user's environment. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Note! Caution! Warning!
El Viernes, 3 de Agosto de 2007 02:06, Randy McMurchy escribió: Lately I've been noticing in the book that there is a huge amount of Note Warning and Caution boxes on the various pages. Some of them for rather trivial things. As I see it, admonitions are good if used when they are actually necessary to make more prominent some very important issue. When admonitions are used excessively they tend to lose their original semantic meant. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: DocBook XSL 1.73.0 Released
El Miércoles, 25 de Julio de 2007 00:21, Randy McMurchy escribió: Keep in mind that the .0 versions of the stylesheets are not the stable series. And in this case it is a truly beta version due the big changes on how the tarball and documentation is generated. Actually we are using the 1.73.0 code (the docbook-xsl-snapshot dir was updated two days ago), but we use only the XHTML and FO part of the code and our customization layout is hidding the possible non-yet-reported bugs. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Bad rendering on new xsl
El Martes, 10 de Julio de 2007 01:02, Dan Nicholson escribió: Manuel, I just noticed that the some links on the hal page in the gnome-python section overlap in my browser. I'm using firefox2. http://www.linuxfromscratch.org/blfs/view/svn/general/hal.html It seems like the problem is listitem with ulink vs. listitem with xref. Any ideas? Is a CSS issue. Now by default nested list are compacted to reduce vertical spacing in TOCs and Changelog. It look fine when the item contains only plain text or internal links, but external links are rendered is monospace font, that is a little bigger than the normal font. Fixed it now. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Updated the book rendering framework.
Hi, The BLFS book sources has been updated to use the new LFS-XSL Stylesheets. Please, let me know if some issue with the new framework is found. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: New book validation procedure?
El Sábado, 7 de Julio de 2007 15:06, Randy McMurchy escribió: Hi all, This is a question for Manuel, and FYI for everyone else. There is still a Makefile target of 'validate' in the BLFS book Makefile and the commands for this have not changed. However, noted in the rendering section of the Makefile, it must first run the Makefile target 'validxml', where the first thing is to echo to STDOUT Validating the book The validate target just validate the XML filis, nothing more, like before. The validxml target is a convenience target added to address two issues: make sure that the book sources are valid before processing, and improve rendering time when several outputs will be generated at the sane time (e.g, make all) Both targets do the same: validating the sources. But the second one dump the output to a *-full.xml file with Xincludes and entities resolved that is used to generate the actual outputs. And another question (this one because I'm ignorant about Makefiles). Best I can tell from the Makefile this is how rendering is done: 1. Run the Makefile target 'blfs'. When oly make is called, the first target is used. Thus a plain make is the same than make blfs. 2. The 'blfs' target first calls the 'validxml' and 'profile-html' targets. Yes, it depends on both. 3. The 'profile-html' target first calls the 'validxml' target. Yes. if you want to run only profile-html you need be sure that validxml is run before. So, my question is this: how does the 'make' procedure know not to run the 'validxml' target twice, once called by the 'blfs' target and again by the 'profile-html? Thats how makefile dependencies works. It first resolve dependencies to know in what order each target must be run, removing duplicated ones. Shouldn't we clean up the file(s) left in the /tmp directory after the completion of the work? They are placed in the /tmp dir, thus theoreticaly deleted after each reboot. And they are overwritten when running againg the target, thus there is no need to worry if someone altered they. That files could be deleted by the Makefile, but I don't see the need to do it and could help to track rendering issues. Actualy I was thinking on make the /tmp directory configurable via a makefile envar (like V=1 is for verbose output) to allow the user to select where to place that temporaly files. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: New book validation procedure?
El Sábado, 7 de Julio de 2007 16:18, Randy McMurchy escribió: What I'd like is to not have to validate every time the book is rendered. I trust the editors to do their job and validate before committing changes. There should be no need to validate, so please let me know how to render without validation. By default, xsltrproc do the validation, but don't output the same info that xmllint. Thus now you have the xmllint output when parsing index.xml while resolving Xincludes and entities with no performance lost, and without the need to do a separate validation process. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: New book validation procedure?
El Sábado, 7 de Julio de 2007 16:13, Randy McMurchy escribió: M.Canales.es wrote these words on 07/07/07 08:55 CST: My background is that *knowingly* leaving stale files in /tmp is bad practice. To each his own, I suppose. To can depure xsltrproc or FOP warnings, that files are required. Thus we have several options: .- To keep the current status. .-About how to handle temp files: remove it by default, addig a Makefile switch to not delete it. That meant that a editor must rebuild at least three times the book (normal render, render not deleting that temp files, and render toi be sure that the issue is fixed) if some warning is output .- About where to place they: to keep they in /tmp or add a $(TMP) envar defaulted to /tmp, $HOME/tmp, or $(BUILDDIR) -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: New book validation procedure?
El Sábado, 7 de Julio de 2007 16:42, Randy McMurchy escribió: How do I render without doing some sort of validation process first? A sort of validation was done also in the old Makefile when only xsltproc was run. But their output was not actualy useful. Thus a validate target was added. The current validate target is keep only for compatibility and for that editors that validates the sources but don't want to generate the html/pdf files. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: New book validation procedure?
El Sábado, 7 de Julio de 2007 16:51, Randy McMurchy escribió:
we don't render a PDF or nochunked HTML on a daily basis.
As the BLFS editor you should do it from time to time to be sure that alll is
sane.
Plus, that output formats, or at least the PDF one, should be available
on-line also for development books.
All this stuff to support make all is really unnecessary, as it really
will never be used.
Do
svn up -r6837
time { make ; }
svu up
time { make ; }
If you see some perfonmance lost, we could start discussing if the current way
to generate the chunked output is good or not.
--
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/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: New book validation procedure?
El Sábado, 7 de Julio de 2007 16:53, Dan Nicholson escribió: Thinking about this a little more, I believe there should be a separate directory not in /tmp. These aren't exactly scratch files. blfs-html.xml and blfs-full.xml are meant to be accessed by multiple targets. Things that go in /tmp should be created and cleaned up right away. How about RENDERDIR = $(HOME)/blfs-render createdir: $(Q)[ -d $(RENDERDIR) ] || mkdir -p $(RENDERDIR) clean: @echo Cleaning up... $(Q)rm -rf $(RENDERDIR) validxml: createdir That might be a solution. If opting by that, I prefer $(BASEDIR)/temp-files or something like that to keep it centralized. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: New book validation procedure?
El Sábado, 7 de Julio de 2007 17:22, Dan Nicholson escribió: On Sat, Jul 07, 2007 at 05:04:39PM +0200, M.Canales.es wrote: That might be a solution. If opting by that, I prefer $(BASEDIR)/temp-files or something like that to keep it centralized. OK, I wasn't sure about polluting $(BASEDIR). What do you think of this? Look at r6850. I don't know how to do that the rm -f will be done only as a last target :-? -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: New book validation procedure?
El Sábado, 7 de Julio de 2007 17:22, Dan Nicholson escribió: On Sat, Jul 07, 2007 at 05:04:39PM +0200, M.Canales.es wrote: That might be a solution. If opting by that, I prefer $(BASEDIR)/temp-files or something like that to keep it centralized. OK, I wasn't sure about polluting $(BASEDIR). What do you think of this? ~/tmp is an acceptable solution. But that put clean as the default target ;-) I'm on that ... -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: New book validation procedure?
El Sábado, 7 de Julio de 2007 18:40, Dan Nicholson escribió: Looks pretty good, except there's a ~$(RENDERTMP) now. Gr, I should be quiet today I don't know if there's a surefire way to make it run last. That's the issue Just make a separate clean target. A separate clean target will be almost identical to that new tmpdir target, I see no need top create one. If someone want to remove that files after generating the book, just run make tmpdir. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: r6853 - trunk/BOOK
El Sábado, 7 de Julio de 2007 18:49, Randy McMurchy escribió: xsltproc --nonet -stringparam chunk.quietly 1 -stringparam rootid 0 ROOT_ID must be set to the empty string. In the Makefile ROOT_ID= on command line -stringparam rootid That setting is used to render only a subset of the book, eg a part, chapter, or sect1, instead of the full book. To do it, set the para to the ID value of the subset you want to build. That is a feature long time requested that hasn't can be implemented until now. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Test Results for Xinerama and JDK6
El Miércoles, 27 de Junio de 2007 09:01, DJ Lucas escribió: Also, anyone know if the pdf book is a go with the new FOP? Guess I could build and find out, or save if for tomorrow. With FOP-0.93 you must to use the stylesheets used in the new-xsl branch: svn://svn.linuxfromscratch.org/LFS/branches/new-xsl Also a small change is needed on the Makefile. Replace sed -i -e s/inherit/all/ blfs.fo by sed -i -e 's/span=inherit/span=all/' blfs.fo I'm using the pre-compiled binary from fop-0.93-bin-jdk1.4.tar.gz package, thus testing the source code compiled against current JDK will be very appreciated. Note: when rendering the BLFS PDF you will see some warnings about body and line overflows. They will be fixed when updating the books to use the new stylesheets. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: xfce update
El Lunes, 14 de Mayo de 2007 17:48, Alexander E. Patrakov escribió: 4) I would prefer to see a description for each XFCE subpackage, but I need XML help from Manuel in order to do this (not sure where it goes) The question is, where should that descriptions be placed? It could be in the package section, to let users to know for what each sub-package is before installing it. Or could be placed in the content section, splitting the installed programs and libraries on an by-sub-package layout format. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[new XSL] Finished LFS and BLFS rework
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 inputs. I would have solved all concerns and complaints about the LFS/BLFS outputs and the stylesheets layout before start working on HLFS and CLFS integration. Please, keep the discussion on the lfs-dev list. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[new XSL] BLFS chunked output ready for comments
Hi, Like the subjects says, the stylesheets revision in ready for comments on the chunked XHTML output. I have not revised all the pages but the general look should be near identical to the current one regarthless the several changes on the surrounding xhtml code (a diff will generate a 5.5M file). To test it, just do a svn export of the BLFS sources and replace the stylesheets directory by a svn co of the new-xsl sources (a svn switch don't work due that they are on different repositories). The most noticeable look change is that now all chapter pages have a TOC and that the firsts sec1 are o a separate page. There is still some issue that I want to solve: - Rewritte the Last updated on ... templates to not use the footnotes engine - In chapter pages, to move the introductory text above the TOC - To merge the LFS and BLFS CSS code - Plus, of course, any other fixes or changes you would I'm waiting your comments. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [new XSL] Ready for inputs.
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 was thinking also about that. The code was committed some hours ago.
Now the PDF have only 254 pages:
http://www.lfs-es.info/new-lfs-book/fop1-try2-lfs-book.pdf
It would also be nice to solve the problem of long urls that cause ugly
spacing when the text is fully justified. Examples are: page 13
(section 1.5), page 14, page 206 (section 7.5), page 217 (7.12.1).
The last paragraph on page 224 (8.2) also suffers from the
long-name-spacing-problem.
These word spacing issues vary a bit in 'badness', but it would be nice
if there were optional (zero width space) breaks at slash ('/') and
underscore ('_') characters.
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.
--
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/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [new XSL] The Index generation
El Jueves, 29 de Marzo de 2007 18:44, matthew escribió: My personal preference would be to have the 'Up' link point to a per-chapter index, I suppose that you meant per-chapter TOC, right? I agree that that's the most logical target for the Up links. I think to remember (not full sure) that was decided to remove the chapter TOCs from PDF output to reduce the pages size of the hard-copy LFS-6.0 book. And removed also from HTML output to have the same look in both outputs. Is for all you to decide if re-add it on both outputs, only on HTML output, or none. or, failing that, remove it entirely as the only other sensible place I can think of it pointing to would be to the main index.html page, which is where 'Home' already links to. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Tidy CVS
El Martes, 27 de Marzo de 2007 20:23, Dan Nicholson escribió: But, if you're offering to test, I'd say anything with pre-LFS-6.2 autotools would be good. Those versions were autoconf-2.59, automake-1.9.6 and libtool-1.5.22. It build and work fine on a LFS-6.0 system (I should to update my working system some day ... ) -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [new XSL] The Index generation
El Lunes, 26 de Marzo de 2007 22:25, Dan Nicholson escribió: Looks OK to me. I don't really like that huge longindex.html. But that's just my vote. We should probably wait until Matthew gets back before making a final decision. I agree, Matthew and Randy are the ones that should take the decision. If you could do that in the xsl branch, that would be great. I have an idea of how it would look, but I'm not certain. I think you should feel free to run any experiments in that branch. The new-xsl branch don't contains the book XML files. Yes, if this new Index is implemented we will need to create a branch on each project book to make the XML changes and do a full merge when ready (a lot of work for me). I'm making now a POC with only Bash, Bzip2, and Ncurses and using the upstream Index code to can have a global idea about how it works and what need be hacked. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [new XSL] The Index generation
El Lunes, 26 de Marzo de 2007 22:59, Randy McMurchy escribió:
For that little of time, the convenience of having everything
together seems a bit better than the alternative.
I'm indifferent about do the change or not, except that if doing the change I
will have a lot of work changing the indexterm tagging on all xLFS books.
But my obligation as XML/XSL maintainer is to say that there is that
posibility and let decide the comunity what to do. If there is some interest
on that index split I will do it, if not I will fix the current
implementation.
Pd: In the POC the pages are splitted properly, but the links are missing.
Looks like there is a bug in the DocBook-XSL code when using both zone and
type attributes in {indexterm}.
--
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/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: Dash
El Jueves, 15 de Marzo de 2007 20:52, Ag. Hatzimanikas escribió: Okey my last offer... I've finished 2 years of college, but I still have 2 more to do. Then you have two more college years than I ;-) -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: A minor diff to update the vim patchlevel and a question.
El Jueves, 8 de Marzo de 2007 07:31, Ag. Hatzimanikas escribió: I will create the ticket just to update the page then,unless someone has a good reason to move the vimrc contents into the vim.xml. IMHO, configurations used only by gvim should be discussed on vim.xml but all others (except maybe the ones already discussed in LFS) should go in vimrc.xml. I.e, in vimrc.xml page is created an ampliantion of the simple vimrc configuration file created in LFS, and in vim.xml page another ampliation is made with graphic stuff. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Update scripts
El Miércoles, 24 de Enero de 2007 20:02, Bruce Dubbs escribió: OK, I found and fixed two problems. Looks like the remaining one in with the script that updates www.linuxfromscratch.org/patches/downloads/ The firefox and thunderbird patches are in the patches svn repo but not in the patches web site. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Dead Links
El Miércoles, 24 de Enero de 2007 21:29, Randy McMurchy escribió: Hi all, Using the wget list provided by Manuel, it is fairly trivial to check for bad book download URLs. Here is one run from just a couple of minutes ago: Note: For that packages that have both HTTP and FTP dowmnoad URLs only the FTP one is dump to that wget list. If you want to test also the HTTP links, say me to do a small change in the XSL code. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Dead Links
El Miércoles, 24 de Enero de 2007 21:39, Randy McMurchy escribió: Yes, please. Even if it is a different target. Properly working, this would be invaluable as a way to periodically check all the download URLs. OK. I must to review and fix also additional files URLs tracking (*.mozconfig files and and others links that are not packages or patches, if any), thus wait the update for tomorrow. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS package repo
El Domingo, 14 de Enero de 2007 16:13, Justin R. Knierim escribió: Thanks Manuel. Welcome back from holidays travel! A normal wget list for all of BLFS would be perfect, since I can compare the list to the real files on the server. Also I'm only interested in packages that have changed since the packages repo was last updated, since there are other things that can happen like me accidentally deleting a symlink or file or old versions left around or other cases I can't think of. It is easy for me to basename the URL's, get the package names and compare with a find ran through basename. I hope that makes sense. Of course I'm always open to suggestions or ideas. OK, starting the work on a plain wget file generator. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Released jhalfs-2.1
The jhalfs development team is pleased to announce the release of jhalfs-2.1. New features in this version: - Better support for CLFS Sysroot book - Added support for CLFS Embedded book - Several bugs fixes and code clean-up The jhalfs-2.1 tarball can be downloaded from http://www.linuxfromscratch.org/alfs/downloads/jhalfs/stable/jhalfs-2.1.tar.bz2 The list of supported books can be found at http://wiki.linuxfromscratch.org/alfs/wiki/SupportedBooks Please, try it out and send any comments or bugs you find to the alfs-discuss mailing list. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS New Management
El Viernes, 15 de Septiembre de 2006 18:19, Bruce Dubbs escribió: I want to thank all the past contributors to BLFS in making the book the wonderful resource that it is. Thanks you for all the work done making BLFS what it is now. In accordance with BLFS prior practices, I am designating Randy McMurchy as the new BLFS Project leader. Please support him as you supported me as BLFS moves forward. Randy is the guy, no dude. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: xLFS Book Licenses
El Martes, 22 de Agosto de 2006 06:13, Bruce Dubbs escribió: He and Ryan are proposing the Open Publication License, http://www.opencontent.org/openpub, for all the books. I've looked at it and it seems to meet the standards of having a recognized license and protecting the books. If it is the community's decision, I have no problem with using this in BLFS. OPL looks fine to me for the textual part of the books. But as you said below, the code (both the code embedded into the books, the XSL code, extra scripts inside the SVN trees used to process the book sources, bootscripts, Udev rules, etc) should use a different license. IMHO a BSD-based one could be the best. About jhalfs, it uses GPL from the beginning and I would to change it to the same decided for book's code, If that can be done and don't will cause conflicts with the included menu and lxdialog files that are under GPL. -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Dead Project? (I hope not)
El Sábado, 19 de Agosto de 2006 06:59, Randy McMurchy escribió: Recently there was a call for funds to replace the Belgarath server. Funds were raised in a matter of days. For all practical purposes, anyone who contributed money, wasted it. That call for funds (and the raising of it) was *many* months ago. There has been no effort to even explain where the donated money went (other than someone bought some hardware, and has it, but won't commit the couple of hours it would take to put it online). That is a good question, where is that new server? The entire LFS project seems to be in the toilet. Am I the only one that thinks this? Am I over reacting? Is there anyone else concerned about the health of the project? In the last weeks there has been a lot of development in HLFS, but Robert is alone. CLFS team is working on the 1.0.0 release, but 1.0.0rc3 was released three weeks ago and no rc4 yet We don't know yet if there is a BLFS-6.2 release planned and for when. LFS need be updated to Glibc.2.4 and to use a new set of kernel headers, but no discussion about that yet. In the last month there has been more development discussion in alfs-discuss that in all other list. Yes, I'm concerned also :-/ -- 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/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Obsolete XML code for jhalfs
Hi! Several month ago [keywordset] tagging blocks was added to the book sources to support the old jhalfs code. With the new under development jhalfs code, plus due that now packages on the FTP mirrors are stored in the same format that upstream packages, that XML blocks are unneeded. I would to remove that tags this weekend, if there is no objetions. Of course, if someone want to remove it from files edited before Saturday, feel free to do it. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Obsolete XML code for jhalfs
El Miércoles, 14 de Junio de 2006 23:26, Randy McMurchy escribió: 1. Wait until I've committed the GNOME update as my sandbox has many, many changes right now. Many files have been added, and/or touched. Your changes and mine would probably merge, but why take the chance? There is no hurry on doing the removal (nothing use/depend on that code, thus nothing is broken), then I can wait until after that big GNOME update. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Generating BLFS books in build order
Hi, As part of the new BLFS support in jhalfs we can now to auto-generate BLFS books in linear build order for any target package or meta-package. A few examples of generated books can be found here: http://www.macana-es.com/pruebas/ Maybe that parser could be useful also as an stand-alone tool outside jhalfs. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Inconsistency on MTA dependencies look
Hi, In several pages we have, into the dependencies blocks: xref linkend=sendmail/ (or another ulink url=../server/mail.htmlMTA/ulink that provides a commandsendmail/command command) That causes that the MTA link look like an external link, instead of a cross-reference to another page inside the book. That is inconsistent and annoying. I propose to change that to simply: a xref linkend=server-mail/ ( that provides a commandsendmail/command command) Adding, of course, the appropriate xreflabel=MTA to server/mail/mail.xml That will do that dependencies on a MTA will look like current dependencies on X, i.e., pointing to a generic internal page. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Xorg7 dependencies
There is few things with the Xorg7 dependencies listed in the book that I have not very clear. - Xorg Libraries isn't listed as a dependency for any other Xorg-* section, only for Mesa. Is true that any other Xorg7 package requires Xorg Libraries? - Mesa is a recommended dependency for Xorg Applications and optional for Xorg Server. I think that if the user want to use a third-part video driver like Nvidia, Mesa isn't needed at all. If that is true, maybe a note should be added. - Mesa is listed also as an dependency for libtiff, but libtiif have also an optional dependency on X, that already includes Mesa. Isn't that redundant? -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Xorg7 dependencies
El Lunes, 22 de Mayo de 2006 21:18, Randy McMurchy escribió: However, I do see some merit in the original thought behind it being put in. If we could state it clearer, that if you have Xorg-7 installed, including the Mesa package, you don't need to install a Glut library as one is already installed, then by all means it should be there. If Xorg-6.9 of XFree86 are installed, Mesa is also included with they. Then, IMHO, the Glut library is needed only when using Xorg7 without Mesa installed. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Libxml2 and Python
Hi In the libxml page we have currently this note: Some packages which utilize libxml2 (such as GNOME Doc Utils) need the Python module installed to function properly. But lbxml2 is a required dependency for GNOME Doc Utils (ScrollKeeper -- libxslt -- libxml2) Based on that, I think that Python should be a Recommended libxml2 dependency. PD: As a side effect, that change will prevent the circular dependency lbxml2 -- lbxslt -- libxml2 in the new jhalfs code (under development) while allowing to build the Python module. PD2: The above jhalfs fix could be achieved also by other ways, like removing role=optional from the second optional dependencies block. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Libxml2 and Python
El Viernes, 19 de Mayo de 2006 23:17, Randy McMurchy escribió: I'm going to have to disagree with you on this one, Manuel. We cannot legitimately say the Python should be recommended. What if one doesn't want to install GNOME (probably 95% of the readers)? Then maybe how that optional blocks are written should be changed. I don't see logical to have and Optional block for two testsuites dependencies and other Optional block for one testsuite dependencie plus a dependency required to build a pluging that other BLFS package depend on, while Python is listed in both. We can't recommend stuff because it will make Jalfs easier. :-) When you will learn to write properly jhalfs? And like I said in PD2, jhalfs can be fixed in other ways. There is several other issues most hard to solve than that. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Xorg7 sub sections
El Jueves, 18 de Mayo de 2006 22:22, Bruce Dubbs escribió: I disagree. It is a lot of *programs* and *libraries* that together compose one *application*. You don't need all the pieces, but then you don't need all the libraries in kdelibs or programs in kdebase either. The difference is that Xorg7 is several separate packages, like Gnome. Not few packages including a lot of apps, like KDE. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: gimp-help-2-0.10
El Viernes, 12 de Mayo de 2006 22:52, Dan Nicholson escribió: xsltproc is invoked with the stylesheet profile.xsl. Here's the contents of that file: === ?xml version=1.0 encoding=utf-8? xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform; version='1.0' xsl:import href=http://docbook.sourceforge.net/release/xsl/current/profiling/profile. xsl / To can process that, at least Doc-Book-XSL 1.50 (due profiling support) is required. !-- Generate DocBook instance with correct DOCTYPE -- xsl:output method=xml encoding=utf-8 doctype-public=-//OASIS//DTD DocBook XML V4.3//EN doctype-system=http://www.docbook.org/xml/4.3/docbookx.dtd/ Plus, to validate generated files DocBook-XML 4.3 is needed. I think that both are required dependencies for documentation generation. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Esound documentation
El Sábado, 6 de Mayo de 2006 21:14, Randy McMurchy escribió: Could we discuss the 'role=docs' used in that patch? It isn't anywhere else in the book. Should we start using that? I think not, but it should be discussed. role=root may have special meaning one day (and perhaps for jalfs, already does). I think also that not. At least has no use in the present. I we (the blfs editors and/or the jhalfs team) need that or something similar in the future, we could to discusse it then. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Esound documentation
El Sábado, 6 de Mayo de 2006 21:35, Randy McMurchy escribió:
I can certainly see optional installation features to be tagged
somehow or another as optional. And 'role=docs' may end up being
adopted. That way, for jhalfs builds, one would only have to say
docs=yes or docs=no or whatever flag you guys use and then everywhere
there is optional docs installation, it would turn it on or off.
Thanks for thinking on jhalfs support.
I need yet to rethink how to integrate BLFS into it after the big jhalfs
changes and feartures additions that we are doing now for {C,H}LFS.
I hope to have something better than the current implementation before BLFS
release. This is a must now due that nALFS profiles are no longer
maintained.
But as Manuel said, we could discuss it and implement it when and
if it is ever desired.
Yes. I prefer to not polute the sources with not discussed and documented tags
and/or attributes.
--
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-ES: http://es.tldp.org
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: udev rule line length
El Viernes, 5 de Mayo de 2006 19:01, Bruce Dubbs escribió: In the alsa utilities section, we have a long line in the instructions about creating a udev rule. Evidently, udev does not support the common practice of allowing a backslash/newline combination for extending a logical line to a new physical line. http://www.linuxfromscratch.org/blfs/view/cvs/multimedia/alsa-utils.html Does anyone know how we can go about shortening this line? Try this: cat /etc/udev/rules.d/15-alsa.rules EOF # Give the audio group ownership of sound devices SUBSYSTEM==sound, GROUP=audio SUBSYSTEM==snd, GROUP=audio # ALSA Devices # When a sound device is detected, restore the volume settings KERNEL==controlC[0-9]*, ACTION==add, NAME=snd/%k, \ RUN=/etc/udev/scripts/alsa-restore %n KERNEL=hw[CD0-9]*, NAME=snd/%k KERNEL=pcm[CD0-9cp]*, NAME=snd/%k KERNEL=midiC[D0-9]*,NAME=snd/%k KERNEL=timer, NAME=snd/%k KERNEL=seq, NAME=snd/%k EOF That should to work, except for cat commands where $SOME_ENVAR, if any, must be preserved. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Chapter 24. X Window System - visual changes
El Domingo, 30 de Abril de 2006 21:27, DJ Lucas escribió: As far as the blank pages, I hadn't noticed them earlier. They appear in the gnome section as well, but the rendered book only includes the second and third as far as I can tell...that's odd. That should be fixed now with r5986 No empty files should be created and all links should to point to the proper files. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Chapter 24. X Window System - visual changes
El Domingo, 30 de Abril de 2006 21:53, Bruce Dubbs escribió: There is a blank page Chapter 25. X Window System Environment http://www.linuxfromscratch.org/~dj/blfs-x7-temp/x/ch25s04.html Yes. And also on the Gnome sections in the master on-line book. I'm trying to figure out wy that dummy pages are created now. They where not created when developed the hack :-/ -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Chapter 24. X Window System - visual changes
El Domingo, 30 de Abril de 2006 21:27, DJ Lucas escribió: As far as the blank pages, I hadn't noticed them earlier. They appear in the gnome section as well, but the rendered book only includes the second and third as far as I can tell...that's odd. Manuel mentioned that the dummy files weren't there before, so what was the original hack for this? Inline in the chapter file? Well, I think that the dummy files weren't there before, but maybe I'm wrong and nobody noticed they until now :-? -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Editing Questions
El Jueves, 20 de Abril de 2006 00:06, Dan Nicholson escribió: What I can't figure out is, how do I make that patch available in patches/blfs/svn? I can't figure out how patches appear there. That is handled by patcheslist.xsl and the script that render the book ;-) -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: SPAM Problem
El Martes, 18 de Abril de 2006 18:48, Bruce Dubbs escribió: Non-member email would go to /dev/null I could to agree if instead to /dev/null that mails are keep awaiting moderator approval. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: SPAM Problem
El Martes, 18 de Abril de 2006 19:33, Bruce Dubbs escribió: Would you like to be the moderator? No problem, but could be better if all editors are moderators. If after some days the number of retained mails/day is excessive, we can then to do the /dev/null redirection. That could be valid for all *lfs-* lists. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Gcc-4.1
El Lunes, 17 de Abril de 2006 20:15, Andrew Benton escribió: Is that wise? As it stands LFS is out of date. Old gcc, old glibc, old kernel headers. As soon as trunk moves to a newer toolchain everyone will start using that. Why waste effort releasing a book that's already obsolete? Due that a newer toolchain will need at least another 2-3 months of testing and issues fixes. We need made more frecuent and well tested stable releases. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: User Notes - Let's Make Something Happen
El Sábado, 15 de Abril de 2006 21:52, Dan Nicholson escribió: So far, it's looking like all lowercase is in the lead with one vote by Archaic and a possibly implicit vote by Randy judging by how you've entered them on the book pages. I'm indifferent. Bruce? I'm also for all lowercase, including the renaming of current Wiki pages. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: User Notes presentation
El Domingo, 9 de Abril de 2006 21:51, Randy McMurchy escribió: and here's what Manuel suggests: para condition=html role=usernotesUser Notes: ulink role=usernotes url='blfs-wiki;/OpenSSL'//para The only difference is that Manuel likes to have the role=usernotes in the para *and* ulink tags, whereas Bruce said in just the para tag. Not, sorry, not noticed that extra usernotes until now. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: User Notes presentation
El Jueves, 30 de Marzo de 2006 20:05, Bruce Dubbs escribió: Where the /sect2 is the first one in the page. ... except if the page isn't a package page. In that cases the link or links will be placed depending on the context. Right? -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Adding Wiki stuff to all the package files [was: Re: Xpdf-3.01]
El Lunes, 27 de Marzo de 2006 19:15, Randy McMurchy escribió: 1. Loop through the book looking for .xml files that have a sect 1 ... header. Searching for role=package will skip all no packages files. 2. Get the name of the package from the 'xreflabel' of the sect 1 ... header. 2. Use a sed to insert the wiki stuff before these lines in each file (I'm almost certain each file would have this): /sect2 sect 2 role=installation A few ones has a role=kernel section on top of the installation one. Could be more safer to let sed to insert the wiki stuff just before the first /sect2 occurrence. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Placement of Links to the Wiki in BLFS
El Miércoles, 1 de Febrero de 2006 03:02, Bruce Dubbs escribió: There has been some discussion of where to place a link to User Notes on BLFS pages. After reviewing the messages, I want to get the opinion one more time from the members of this list so we can standardize. I vote for placing it at the end of the Introduction section into a [tip] admonition box. Plus, to add the relevant introductory text mentioned by Randy into the introduction/wiki.html page. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Dependency Viewing
El Miércoles, 1 de Febrero de 2006 10:14, Richard A Downing escribió: All that is needed is a simple list in the form, e.g.: libmng: libjpeg lcms for each package and a blank list for those with no deps. libjpeg: lcms: bc: all wrapped up with a bit of makefile magic. You can then type: 'make libmng', and get a list in the right order to build. Anyone suggest how to do this? That is very similar to what jhablfs do. Don't seem very hard to create only that dependencies Makefile. Could be enought using a simple XSL script. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: RFC: BLFS Wiki
El Domingo, 22 de Enero de 2006 20:56, Bruce Dubbs escribió: 1. The section in the book is formatted as a sect2. I'm not sure this has the proper appearance. What about this? [tip condition=html] [title]User Notes[/title] [para][ulink url=http://...[/ulink] [/tip] -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: RFC: BLFS Wiki
El Lunes, 23 de Enero de 2006 19:10, Bruce Dubbs escribió: Doesn't validate, at least where it is located right now. Yes, it should be inside an existent sec2 bnlock. Perhaps it would be better to just insert [para condition=html class=usernotes]User Notes: [ulink url=http://...[/ulink][/para] or [formalpara condition=html] [title]User Notes:[/title] [para][ulink url=http://...[/ulink] [/formalpara] There are several way to skin this cat ;-) -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: New BLFS Editor
El Miércoles, 7 de Diciembre de 2005 17:37, Bruce Dubbs escribió: Please help me in welcoming Andy to the team. Welcome Andy, that is a very good news :-) -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Automating BLFS
El Lunes, 28 de Noviembre de 2005 16:33, Bruce Dubbs escribió: Jeremy Huntwork wrote: Well, if you're concerned about disrupting automation, the prompt for the choice could come right away, as soon as you enter make. It could traverse the dependencies and make sure all necessary choices are made. Yes, this would be a nice option. When given a choice, take both. :) How about a switch/configuration option that would specify: CHOICE=default or CHOICE=prompt This could also be overridden by additional variables: MTA=postfix|sendmail|exim X=xorg|xfree86 KERBEROS=heimdal|krb5 other options could be QT=/opt|/usr KDE=/opt|/usr I'd also consider a variable OPTIONAL=packageA,packageB,... That would add in optional dependencies as desired by the user. These are the main alternative packages/options that I can remember off the top of my head. I'd have to go through the book to get a comprehensive list, but we are just talking concepts right now. -- Bruce -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Automating BLFS
El Domingo, 27 de Noviembre de 2005 19:03, Randy McMurchy escribió: I personally don't see the benefit. Are you using customs scripts to build the BLFS packages or are you copy-and-paste directly from the book? Automating LFS is one thing. BLFS is a whole different animal. Agree. For BLFS only a semi-automatization is possible. We can create the base scripts and Makefile, but the user will need to read the book to figure-out what changes should do to those scripts and Makefile to install the packages he want in the way that he want. There are simply too many intangibles that will have to be addressed: configuration, That is also true for any distro. The user must to configure several packages after installation to can use it which package to use when you have a required dependency of packageA or packageB, User choice, via a command switch or editing the Makefile. dependencies not having instructions in BLFS, I hope that no Required ones. do you run the test suites. Already handled. I could go on but I think you get the message. Yes, there is many issues that must be take into account to can do the system work. We have close to, or at, 100 bugs in BZ. Adding an automated build system is going to increase this plus put a drain on the Editor load. I doubt it. We already have some packages in BLFS that won't build using GCC4. And now you want to add more complexity. What complexity is added by those small tags changes? When it place, their maitenance work will be negigible. I realize that now it will be suggested that Jeremy and Manual will be glad to help out in getting this done, however, my belief is that there will be one issue after another which will have to be addressed. I hope that no others requiring XML changes. And that changes are due that there ir no other easy way to extract that info. I suppose one thing is that I am just not a fan of automated builds. This may be tainting my opinion. Maybe. I was trying to avoid any change on the XML due that I was sure about your answer :-/ -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Patches md5sums
El Jueves, 3 de Noviembre de 2005 19:46, Randy McMurchy escribió: However, creating a directory for BLFS SVN patches and adding symlinks to the patches in this directory, would mean that we would only have to update the patches location entity in the book. That was the method previously used in HLFS, but migrated now to the method used in LFS: the patches are automatically recollected from the book's sources, pulled from the patches SVN repo, and copied to a directory under www.linuxfromscratch.org/patches/ each time that the online book version is rendered. Requisites: find the old blfs-patches.xsl stylesheet (I should have it in some place), very that work with current BLFS sources, and adapt render-blfs-book.sh to use it. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Patches md5sums
El Jueves, 3 de Noviembre de 2005 20:23, Randy McMurchy escribió:
Thanks for the tip, Manuel. Another thing I now remember about having
the BLFS repo is that a message is sent to -book if there is any
patches missing or if one that is not referenced in the book exists
in the repo.
Actually the original stylesheet can be foud here:
http://archives.linuxfromscratch.org/mail-archives/blfs-dev/2005-January/009021.html
I will test soon it some fix is needed (most possible for the OOo patches)
I suppose this would still be an easy thing to set up.
That feature is already in the render-{b}lfs-book.sh scripts. The patches copy
is handled in the same way as the book rendering: if the step fail the
process is stopped and a mail is send.
Plus, the stylesheet and the resultant script can be run at any time by an
editor logged in belgarath in debugging mode ;-)
--
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-ES: http://es.tldp.org
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: Patches md5sums
El Jueves, 3 de Noviembre de 2005 20:34, M.Canales.es escribió: I will test soon it some fix is needed (most possible for the OOo patches) I have ready the revised patches-script.xsl stylesheet to match current BLFS-SVN, and work fine. But two issues has been catches testing it: .- The php-5.0.5-db43-1.patch patch is missing in the patches repo. .- The fop-0.20.5-jdk_1.5.0-1.patch is miss-named in the patches repo. Both should be fixed regardless if that stylesheet will be used or not. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: libexecdir
El Miércoles, 19 de Octubre de 2005 18:43, Bruce Dubbs escribió: $ grep -R -- --libexec *| grep -v svn|grep -v \~|cut -f1 -d:|uniq This method is more easy to remember ;-) $ grep -rl \-\-libexec --exclude=*base . | sort -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: gcc-4.x installation
El Martes, 20 de Septiembre de 2005 20:14, Bruce Dubbs escribió: I wouldn't think so, but I suppose it is a possibility. Do you have a better wording for the note? May be The instructions below assume that the system is a pure LFS lfs-version;. ? -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: RFC: Using gamin instead of fam
El Miércoles, 14 de Septiembre de 2005 15:50, Tushar Teredesai escribió: I would like to propose replacing fam in the BLFS book by gamin. Is gamin supported by KDE? -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: XSL Stylesheets
El Sábado, 10 de Septiembre de 2005 17:38, Randy McMurchy escribió: Can you explain what these lines in the catalog did, and why you suggest removing them? /etc/xml/docbook is a catalog file used by the BLFS instructuions for DocBook-XML to resolve Public Identifiers due some incompatibilities with OpenJade in the docbook.cat file included with the DocBook-XML package (at least up to xml-dtd-4.2.1, not verified with newest ones). The XSL stylesheets are based on XML-Schemas, then they don't have any Public Identifier associated. That lines was always uneeded fox DocBook-XSL, and maybe the full etc/xml/docbook file is also unneded now. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: XSL Stylesheets
El Sábado, 10 de Septiembre de 2005 19:14, Randy McMurchy escribió: I don't get it. Can you point me to some documentation somewhere that can more clearly explain this for me? For one, I don't understand how you could do rewrite statements for the various DTD versions without using the /etc/xml/docbook file. Could this be placed in the /etc/xml/catalog file instead? Some corrections to my previous post: The Openade imcompatibilities mentioned earlier aren't related with XML catalogs. That was a SGML issue solved some time ago. And the FPIs rewrite staments done actually on /etc/xml/docbook are required due that the DocBook-XML-DTD packages don't have a docbook.xml catalog. But to place that FPIs rewrite staments on /etc/xml/docbook isn't a good approach, IMHO. They should be placed on /usr/share/xml/docbook/xml-dtd-$version/docbook.xml files, one for each DTD version installed. How would you do this without using /etc/xml/docbook? All FPIs and URLs resolution can be placed on a unique file, /etc/xml/catalog or the one specified in XML_CATALOG_FILES, if wanted a there is few entities to be resoleved. When is needed to resolve several entities (several DTD's, XML Schemas, Relax-NG schemas, etc, not only from DocBook, also from other projets), then a modular approach could be good for maintenance purporses. To see a good modular approach and more info about catalogs: http://debian-xml-sgml.alioth.debian.org/xml-policy/xml-catalogs.html -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS Makefile and new scripts.
El Martes, 30 de Agosto de 2005 01:22, Randy McMurchy escribió: There should be something in the stylesheet so that when it encounters installing a boot script, it places a note to cd to the appropriate directory containing the bootscripts. As is, the command would simply fail. That, and many other improvements to can generate a more scriptable output, could need some XML changes to can handle each type of commands in a different way. At this moment we have role=root for root commands (can be used to generate su - before the block and exit after it, but that don't will allow automatization) and role=nodump for blocks that don't must be dumped. Also, a different output is generated when a [replaceable] tag is found, altought I would to find the way to generate envars for that tags and collected they on a separate config-build file. Others specials attributes and/or tags could be added to generate a more usable output, but I don't want to mess with the XML sources without the go ahead from the community, and more important yet, the agreement of the book's editors. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
BLFS Makefile and new scripts.
Hi. I would to add to BLFS the obfuscate.sh script and the dump-commands.xsl stylesheet. Both has been tested in production mode with the LFS book during some weeks with no issues, and work well with BLFS sources. I also would to replace the goTidy script by a for loop in the Makefile, like is done from many time ago in the [H]LFS books. Agree you with both updates? -- 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-ES: http://es.tldp.org pgppd6rFmMfkt.pgp Description: PGP signature -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
The trunk Changelog.
Hi, Now that the trunk Changelog is yet small, maybe we can move on their format to the new layout used in the cross-lfs book. See, for example, the Changelog entries section in http://www.linuxfromscratch.org/lfs/view/cross-lfs/x86/introduction/changelog.html IMHO, that layout is more clean and easy to read. If the change is wanted, I can do it when accepted this propossal. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: The trunk Changelog.
El Miércoles, 17 de Agosto de 2005 20:39, Randy McMurchy escribió: With all due respect to your proposal, Manuel, I will have to vote against this change. BLFS and LFS are much different animals. It would take a bunch of searching through the file to make updates. It is one thing to handle the few package updates that go in an LFS changelog. I would bet that more packages are updated just by updating a GNOME-2 version than in all of LFS during a release cycle. I'm not speaking about the packages and patches sections, that isn't usefful for BLFS. I'm speaking about the real changelog entries, the ones grouped by date and divided by editor/change. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: The trunk Changelog.
El Miércoles, 17 de Agosto de 2005 20:59, Bruce Dubbs escribió: Manuel, can you create a demo page of exactly what you are proposing for BLFS? Yes, I will made the change locally and them publish the new page for review in few hours. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: The trunk Changelog.
El Miércoles, 17 de Agosto de 2005 21:01, Randy McMurchy escribió: That is unnecessary work for Manuel. Just use the link he gave, and then scroll down to the Changelog Entries: section. The work is the same. Only need to publish the page before to do the commit ;-) -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: The trunk Changelog.
El Miércoles, 17 de Agosto de 2005 20:59, Bruce Dubbs escribió: Manuel, can you create a demo page of exactly what you are proposing for BLFS? Ready for review both, the XML and the XHTML: http://www.macana-es.com/pruebas/changelog.html http://www.macana-es.com/pruebas/changelog.xml -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: The trunk Changelog.
El Miércoles, 17 de Agosto de 2005 21:53, Randy McMurchy escribió: I like it. It does appear, however, that you missed removing the date from one entry though. Yes, already catched and fixed on my working copy. Thanks ;-) -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Typo in Docbook XSL Stylesheets section
El Lunes, 1 de Agosto de 2005 21:03, Tushar Teredesai escribió: ill be released 1.69.1. Damn, I have to downgrade. I wish maintainers would start having version numbers that made sense :( In the RELEASE-NOTES.txt file: As with all DocBook Project dot zero releases, this is an experimental release . They allways use that numbers schema ;-) -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: New BLFS Editor
El Jueves, 28 de Julio de 2005 19:02, Bruce Dubbs escribió: Please help me in welcoming Richard Downing (aka TheOldFellow) as a new BLFS Editor. Richard has been contributing to the lists since 2002 and will be a valuable asset to the BLFS Team. Welcome on-board, Richard :-) -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: List of Tables
El Jueves, 2 de Junio de 2005 07:20, Bruce Dubbs escribió: Manuel, can you give us some options here? I vote for removing the TOC link, is more easy and IMHO has nosense to create a List of Tables when there is only one table. Fixed in few minutes... -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Rsync requires ssh/rsh
El Jueves, 2 de Junio de 2005 20:01, Randy McMurchy escribió: However, it's my understanding of the rsync client is that it requires ssh or rsh to work properly. Depend on how is configured the server that you want to conect to. That is very similar to CVS or Subversion. You can to use the internal autenthication method or a more secure external one. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Rsync requires ssh/rsh
El Jueves, 2 de Junio de 2005 20:23, Randy McMurchy escribió: That would make sense. However, the default BLFS build at this point uses ssh as the default transport. Looking at the source code, best I can figure is that unless you pass additional parameters to the configure script, rsync will attempt to use ssh as the transport. The transport is defined at run-time via the --rsh=COMMAND parameter. Actually, the use of rsync client is very similar to rcp. You can to use it to synchonize files between any machines where you have a shell account. To can connect to an rsycnd server is an aditional feature useful when you don't have a shell account on the remote machine. Then, IMHO, for the server part SSH is a reccomended dependencie to can create a more secure setup. But for the client, a note like You may need SSH to can connect to remote host or rsyncd servers is enougth. -- 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-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
