>> That is definitely not wise. There has been a fundamental rule in
>> computing in the 40 odd years of my career: "Only change ONE thing
>>at a time!"
>
>
>Spoil sport
That's how one gets to have a 40 year career in computing!
And unfortunately THAT explains why one might forget to delete
First, apologies to all. It seems I forgot to remove most of the digest
in my last message. 8-(
>the only problem is that it still gives me that error and the there is
>no filelist in /var/state/git/package
Do you have a /var/state directory? There is another variable in git
that identifies it
>However, i'm unsure about the practicalities of future updates to such a
>system. My current, working Gentoo system is running Xorg-7.0, & to
>update to 7.2 it only wants to replace 19 components with newer ones, so
>how 'version-specific' is modular-xorg, & will updating components one
>at a
>I finished to create and tested my own alsa startup script and would
>like to know if there is a number service specific for alsa startup to
>maintain blfs bootscripts compatibility even if I saw that the alsa
>bootscript from blfs-bootscripts is only used to stop alsa and not to
>start it.
I did
I'm preparing to install KDE-3.4.3 on my new LFS-6.1.1 system. The KDE
website has a requirements page that says it needs libarts>=2.3.8. I've
found & downloaded a tarball for libarts-2.3.11. Unpacking kdelibs, I
find it's asking for aRts. I know from a prior installation aRts creates
a libarts
>The problem went after, when I wanted to upgrade to KDE 3.5.2. I've
tried out
>many approach, without success. Here is the problem I get :
>mcopidl compils, but with an error :
David, I'm sorry I don't have a solution for you, but I don't think
there's an easy one. I think it's just that KDE co
