Hi, is SuSEconfig run by smart in a smart way, or do I have to run SuSEconfig manually each time I've used smart? René -- Registered Linux User #324404
On Thu, 3 Nov 2005, René Matth wrote:
is SuSEconfig run by smart in a smart way, or do I have to run SuSEconfig manually each time I've used smart?
smart doesn't know about SuSEconfig yet, but we could simply add a hook to trigger SuSEconfig from smart. Regards Christoph
Op donderdag 03 november 2005 14:09, schreef Christoph Thiel:
is SuSEconfig run by smart in a smart way, or do I have to run SuSEconfig manually each time I've used smart?
smart doesn't know about SuSEconfig yet, but we could simply add a hook to trigger SuSEconfig from smart.
Could you make it in similar as is done for apt, where the backend is configurable and the postscript can be enabled or disabled (using --(no-)postscript). Would this include ldconfig as well? -- Richard Bos Without a home the journey is endless
Hi Richard, On Thu, 3 Nov 2005, Richard Bos wrote:
Op donderdag 03 november 2005 14:09, schreef Christoph Thiel:
is SuSEconfig run by smart in a smart way, or do I have to run SuSEconfig manually each time I've used smart?
smart doesn't know about SuSEconfig yet, but we could simply add a hook to trigger SuSEconfig from smart.
Could you make it in similar as is done for apt, where the backend is configurable and the postscript can be enabled or disabled (using --(no-)postscript). Would this include ldconfig as well?
As SuSEconfig isn't generally triggered by postinstall scripts, we will need to have smart trigger it after each transaction. This won't inlcude ldconfig, which I basically wouldn't recommend to disable. Regards Christoph
Op vrijdag 04 november 2005 09:02, schreef Christoph Thiel:
smart doesn't know about SuSEconfig yet, but we could simply add a hook to trigger SuSEconfig from smart.
Could you make it in similar as is done for apt, where the backend is configurable and the postscript can be enabled or disabled (using --(no-)postscript). Would this include ldconfig as well?
As SuSEconfig isn't generally triggered by postinstall scripts, we will need to have smart trigger it after each transaction. This won't inlcude ldconfig, which I basically wouldn't recommend to disable.
Do you mean with the last line: "run ldconfig, after updating packages"? In apt SuSEconfig and ldconfig are you part of 1 postscript. If the poststript execution is enable both will be executed. I would expect the from a smartpm postscript. -- Richard Bos Without a home the journey is endless
On Fri, 4 Nov 2005, Richard Bos wrote:
Op vrijdag 04 november 2005 09:02, schreef Christoph Thiel:
smart doesn't know about SuSEconfig yet, but we could simply add a hook to trigger SuSEconfig from smart.
Could you make it in similar as is done for apt, where the backend is configurable and the postscript can be enabled or disabled (using --(no-)postscript). Would this include ldconfig as well?
As SuSEconfig isn't generally triggered by postinstall scripts, we will need to have smart trigger it after each transaction. This won't inlcude ldconfig, which I basically wouldn't recommend to disable.
Do you mean with the last line: "run ldconfig, after updating packages"?
I was thinking of RPM postinstall scripts.
In apt SuSEconfig and ldconfig are you part of 1 postscript. If the poststript execution is enable both will be executed. I would expect the from a smartpm postscript.
Sure, that sounds reasonable ;) Regards Christoph
participants (3)
-
Christoph Thiel -
René Matthäi -
Richard Bos