On Thu, Jun 21, 2012 at 06:22:08PM -0700, Fernando de Oliveira wrote:
> > 
> >  Thank you.  My overriding point on this is that we are *all* short
> > of time.  You suggested something, with frequent updates, which I
> > think will use a lot of editorial time whenever there are significant
> > numbers of packages released by xorg.  I'm still doubtful that many
> > of the updates will be beneficial to us (looking at release
> > announcements, often the fixes are for non-linux systems).
> 
> Yes, but for almost all other BLFS, it does not matter, just upgrade
> them. I remember that this was not the case of Gimp. Other than that, I
> feel it is simpler than a major upgrade.

 I only normally upgrade a completed system to fix vulnerabilities.
I might upgrade a package it if I think there is a bug fix which is
useful to me.  I *do* usually use newer xorg, depending on my view of
what it says in the release announcements for the individual packages,
in my new builds, and normally I make several new builds each year.

 You will all know that I prefer fresh builds to keeping an existing
system going : in theory I was going to keep my LFS-6.6 usable, but
in practice the kernel and e2fsprogs that it shipped with were a bit
too old for me to use ext4.  I've also spent time on BLFS-6.3, and
not enjoyed keeping the old versions.  So, I've been happy when my
offers to e.g. get a BLFS-6.8 release prepared were rejected, and
usually happier to use newer versions of packages.

> >  I see that DJ is suggesting something slightly different.
> 
> BTW, I read his post, but have to do it again, to better understand - DJ
> is a very dense writer :-), before trying to reply. So, I am not sure if
> what I am writing here is in contradiction with his suggestion. 
> 

 Yeah, I'm not sure I totally grok what he is proposing, so I'm
leaving his suggestion alone until I can see how it looks.  [ sorry,
DJ ]

> > Your
> > suggestions are often useful, but in your post you proposed that
> > other people use their own time to update things which they have not,
> > so far, felt to be their top priority.  Now do you see why I
> > suggested that you might be a good person to tackle this, since you
> > care about it ?
> > 
> > ĸen
> > 
> 
> I would like to try an accord with you and, of course, DJ. Next time,
> instead of just reporting I upgraded Xorg, I will do in more detail,
> with times, sizes, and you tell me what should I do or redo, in order
> for it to be accepted as a commitment to the book. If everything goes
> right, I will ask you and your pairs privileges to commit it and be
> responsible for minor Xorg upgrades (not major ones).
> 
 What is really useful is patches for the book (i.e. for the xml).
But if you can do that, you can edit [ subject to initial review ].

 Also, I'm not commiting myself to updating anything - in theory,
I've more or less stopped updating BLFS to get back to some other
things (such as painting my models, which is why I'm still up at the
moment, waiting for the thinners on my fingers to dry :) - in
practice, I've got two or three packages to do, and other changes to
propose when Bruce is back.  But I keep dreaming of leaving BLFS to
those who can do it well -

 last year, I was away from both books throughout the summer (managed
to go travelling, twice), but when I came back LFS had changed so
much (glibc and bootscripts) that I had to come back here to get the
things I use, such as nfs, working again.  So, I've *still* got a
backlog of photos to deal with, and I would much prefer to NOT spend
this summer (I suppose that is winter for you) dealing with BLFS.
But I'm soft, and I'll probably spend too much time here.

 For xorg, I suppose it is possible that the only normal changes
across version upgrades are the tarball size, md5sum, space, and
SBU.  My experience with other packages suggests that sort of
minimal update will sooner or later become more complex [ extra
packages / revised build order / other optional dependencies ].

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to