Hey Guys:
So I'm mostly done with adding the sha256 checksum support for yum repo
generation in taskomatic and its fully functional. Now, currently the
way I have it working is, if the Channel or in child channel case (its
parent) is el5'ish or if its a custom channel then we use sha1, else we
default to sha256. This works fine in all cases and specifically for el5.
Now for custom channels, was thinking of another approach, this may be
for spacewalk-0.6 if we have time or do it in 0.7..
So basically, give the user an option to choose which checksum to use at
the channel creation time,
* In the createChannel page, we add a little field for user to chose
which checksum to use for repo cache. With a tip at the bottom that
suggests which option to choose when. for example,
<channel creation page>
Checksum Type for Repo: ______________________ (default to sha1 as its
less breakage prone. Or we can change this to sha256)
tip: Use sha1 if you're using older rpm content such as RHEL-5/Centos-5
Use sha256 if you're using newer rpm content such as Fedora-11.
* If its a null org channel we go by what I have so far and decide by
channel release.
This adds little more extension to what I have but its probably better
in long run.
My take is leave it the way I have for space0.6 and do this improvement
for 0.7'ish.
What do you guys think ?
--
--
Pradeep Kilambi
RHN Satellite Engineering
[email protected]
Phone: +1 919 754 4285
RHCE # 805008680430554
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
