Hi there, On Thu, 17 Aug 2006, 14:15:58 +0200, Mauricio Teixeira (netmask) wrote: > Em Qui, 2006-08-17 às 13:04 +0200, Andreas Hanke escreveu: > > > At least rug runs SuSEconfig after each transaction, and it's _painful_ > > compared to YaST because other than YaST, it doesn't show what it does, > > Well, I've never used rug, so I was not sure about it.
This would be a design error in the first place, I'd say, as rug knows (should know, at least...) about the _whole_ set of transactions, so it should run SuSEconfig just once, which is at the end of the whole set of transactions. > Regarding smart, it's an old request to run SuSEconfig at the end, but > looks like we'll wait for this discussion here to reach a decision so we > would make ours on smart. :) Dunno if this helps others, but apt-get knows about this since quite some time, and it works amazingly well - on i386 (ie. 32-bit) platforms at least. Unfortunately the x86_64 version has a pathname compiled into its shared library (this is on SL-10.0) "libapt-pkg-libc6.3-6.so.2.0.0", which stops running the System::Post:: script(s) (which will call SuSEconfig amongst others): strings -a /usr/lib64/libapt-pkg-libc6.3-6.so.2.0.0 | fgrep /usr/lib /usr/lib64/apt/methods /usr/lib/apt/scripts As you can see the scripts will be looked up in the architecture independent location "/usr/lib/apt" (which is correct FWIW), but they are installed under "/usr/lib64/apt/scripts" unfortunately. Creating a corresponding symbolic link cures that problem: ln -snf ../lib64/apt /usr/lib/apt > And sure running the needed scripts on %post would do the trick, but it > would require a lot of documentation so that the packagers would know > if/when/how/why would they need to do that. No, you don't want to run e.g. "ldconfig" after _each_ RPM you're installing... To be honest, I didn't like SuSEconfig when I first used SUSE Linux (came from Red Hat background...), but I'm not sure what the solution would be that fullfills the same job _and_ with the same efficiency... Cheers. l8er manfred --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
