https://bugzilla.novell.com/show_bug.cgi?id=350747
User lrupp@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350747#c1
Lars Rupp changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lrupp@novell.com
Status|NEW |NEEDINFO
Info Provider| |schlomo.schapiro@novell.com
--- Comment #1 from Lars Rupp 2008-01-10 03:47:14 MST ---
First: Thanks for your script!
Three notes/questions:
1) We try to find out as much as possible automatically - or get it via
commandline. So editing these script (which should not be marked as %config in
RPM) is no option: an update would replace the REPO and KEY values. So the REPO
should be the first argument for the script and the KEY another one (and if no
KEY is given, take the default key from the user running this script).
2) I've little dependency problem already with the "createpatch" script in
inst-source-utils (see #308684 for details). So your script also would add a
dependency for createrepo (and all the python stuff) if we don't find another
solution. I've made a quick hack in createpatch to check for an installed
createrepo or warn the user that he should install this RPM.
So either we also need a check for existance of createrepo (if [ -x
/usr/bin/createrepo ]; then...] or we should think about splitting out the
scripts which create/prepare/edit yum-repositories. What do you think?
3) The gpg signing part should be done by an extra script named "sign" as we do
this in other scripts, too. Here we use a C++ script for this - but a simple
bash script should also do this job.
This new "sign" script should be aware of the following arguments:
-v : verbose
-d : detach sign
-c : clearsign (inline ascii armored => patch-files for <= sles9)
-r : sign rpms
=> My task to provide such a simple script with the next update.
Do like like the suggested changes and provide an adapted script?
--
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.