Issue #295: Provide system mono strong name key - fesco

fesco

#295 Provide system mono strong name key

Closed Opened Dec 11, 2009 by snecker.

= Proposal topic =

Generate mono strong name key and place in buildroots. Or something.

= Overview =

Currently log4net (which I maintain) and nant are locked in a cyclic dependency. This means someone has to do some crazy bootstrapping to get them to build each time. This is annoying the hell out of Spot.

https://www.redhat.com/archives/fedora-devel-list/2009-October/msg01399.html

More details on the problem here:

https://www.redhat.com/archives/fedora-devel-list/2009-November/msg02148.html

= Problem space =

No more bootstrapping. Packages just build.

= Solution Overview =

Generate a strong name key per release and let the builders have access to it at:

/etc/pki/mono/mono.snk

Also see my response here:

https://www.redhat.com/archives/fedora-devel-list/2009-November/msg02152.html

on how Debian handle this problem.

= Active Ingredients =

Mono stack. Log4net, nant, possibly others...

= Owners =

Snecker. Though need input on best way to implement. Spot has been doing the bootstrapping so perhaps he is the best person to advise on this. Maybe Kalev Lember could also be looped in on this.

Thanks FESCO dudes! I won't be able to make the meeting I'm afraid.

kkofler commented Dec 11, 2009

Does this really need to go through FESCo? I think the package with the key should just go through the regular review process and then you need to talk to FPC to get the Mono packaging guidelines updated to mention this (and at the end it'll come back to us as part of the FPC items for approval, but that's usually just a formality).

snecker commented Dec 11, 2009

Replying to [comment:1 kkofler]:

Does this really need to go through FESCo? I think the package with the key should just go through the regular review process and then you need to talk to FPC to get the Mono packaging guidelines updated to mention this (and at the end it'll come back to us as part of the FPC items for approval, but that's usually just a formality).

Happy to do that Kevin and if that is the best solution then will proceed with that. I was only asking it to go via FESCo to get the required eyeballs on it and make sure people are generally happy with that method. I was hoping the the mono maintainer might pick this up but will start a package review process for it anyway. I've already emailed Jon Stanley to ask this to be raised but unless I hear otherwise I'll start a package review process shortly.

Thanks for the fast response.

jstanley commented Dec 11, 2009

Yeah, I think that this is just another new package that you BR. Would be happy to bring it up at the meeting, though.

kevin commented Jan 8, 2010

This was fixed a while back and added to mono-devel.