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
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
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
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
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
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
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:
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
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
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
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 FUNC
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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,
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:
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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,
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
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
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
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
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
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
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
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
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
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,
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
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:
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
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
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
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
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
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:
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
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
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
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
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
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:
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
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:
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
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
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
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,
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
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
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:
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
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
--
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:
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
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
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
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
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
1 - 100 of 118 matches
Mail list logo
