This is a discussion on Upgrade to kdebase-3.2.3-i486-2 loses config files within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Before I take this up to Pat, just wanted to check if I'm ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Before I take this up to Pat, just wanted to check if I'm think right about this. I just installed swaret and upgraded my desktop to the latest 10.0 packages (from the original 10.0 CD packages). In the process it upgraded kdebase which overwrote some of kdm's config files in /opt/kde/share/config/kdm. Checking the install script I see that it only protects the kdmrc file not the other config files in that directory. However the equivalent xdm config files in the x11-6.7.0-i486-4 package are protected, which suggests it's an oversight in the doinst.sh script for the kdebase package. Am I think right here, should I inform Pat? Blumf -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBXHYdMid3IcxolsoRAuAgAJ0RRrfYr0/oSptwyiYCfguy0EEpCwCfaGct 4mqb+WcwJtYK+Xz1V77fZ4k= =4g4V -----END PGP SIGNATURE----- |
| |||
| -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In alt.os.linux.slackware, Blumf dared to utter, > Am I think right here, should I inform Pat? Yeah, I'd inform him. It looks like a simple oversight. - -- It is better to hear the rebuke of the wise, Than for a man to hear the song of fools. Ecclesiastes 7:5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBXKnjlKR45I6cfKARAkoaAKCHcNABZL3FYb49MF9YPU ICMUtEcgCbBqhe LPRExRHkpPAmcLzsJuGF75s= =eG8h -----END PGP SIGNATURE----- |
| |||
| NOTE: This message was sent thru a mail2news gateway. No effort was made to verify the identity of the sender. -------------------------------------------------------- pgp trash troll delete Hicks, Alan 188 Shady Dale Dr Lizella, GA 31052 478-935-8132 +Alan Hicks+ <alan@lizella.network> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > In alt.os.linux.slackware, Blumf dared to utter, >> Am I think right here, should I inform Pat? > > Yeah, I'd inform him. It looks like a simple oversight. > > - -- > It is better to hear the rebuke of the wise, > Than for a man to hear the song of fools. > Ecclesiastes 7:5 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (GNU/Linux) > > iD8DBQFBXKnjlKR45I6cfKARAkoaAKCHcNABZL3FYb49MF9YPU ICMUtEcgCbBqhe > LPRExRHkpPAmcLzsJuGF75s= > =eG8h > -----END PGP SIGNATURE----- |
| |||
| > Before I take this up to Pat, just wanted to check if I'm think right > about this. > > I just installed swaret and upgraded my desktop to the latest 10.0 > packages (from the original 10.0 CD packages). In the process it upgraded > kdebase which overwrote some of kdm's config files in > /opt/kde/share/config/kdm. > > Checking the install script I see that it only protects the kdmrc file not > the other config files in that directory. However the equivalent xdm > config files in the x11-6.7.0-i486-4 package are protected, which suggests > it's an oversight in the doinst.sh script for the kdebase package. > > Am I think right here, should I inform Pat? You are right, one of the shortcomings of slackware's package management is that it doesn't automatically handle config files in packages (computers are made to do these boring things!!). -- дамјан 0 and 1. Now what could be so hard about that? |
| ||||
| ?????? ??????????? wrote: > one of the shortcomings of slackware's package management is that it doesn't > automatically handle config files in packages (computers are made to do > these boring things!!). i don't think there is any package management system that "automatically" handles config files in packages. they only do so because the package maintainer creates his package in the right way. -- Joost Kremers joostkremers@yahoo.com Selbst in die Unterwelt dringt durch Spalten Licht EN:SiS(9) |