https://bugzilla.novell.com/show_bug.cgi?id=229622 ------- Comment #4 from suse-tux@gmx.de 2006-12-19 10:19 MST ------- (In reply to comment #3)
(In reply to comment #2)
Hmm do you want to add some suse-specific stuff?
in a manner that other distributions can do the same, driver based or so. ;)
ok:)
If yes i think this is the wrong way because such a patch wouldn't be accepted upstream.
How do you know ? I have contributed code to PEAR a few times without problems...
Yep - i thought if the code would be suse-specific, sorry!
I think some %post and %postun would be much more easier and we wouldn't need a new patch for the php package.
my goal is to fix this problem, a provide a tool to automatically create spec files for any pear package to be rolled out in the buildservice, with very lilte or no manual intervention.
Ah ok. Well such a tool would be great for "normal" users who just want to build a pear package but I wouldn't use it if i want to build "good" package (i don't want to say that your improved tool wouldn't build a good package (i'm just referring to the spec file which i get after "pear5 makerpm <pear-module>)). The question is how to make the new installed rpm known to the pear packagemanager (and how to remove it). I would suggest to use some pear commands in the %post and %postun sections - or is there a better way (or will the extended pear do it?) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.