On 11/09/2009 01:24 PM, Bill Nottingham wrote:
> Peter Jones (pjones@xxxxxxxxxx) said:
>> Okay, and now for the conversation about this.
>>
>> I think betanag should be set in a different package, such as fedora-release.
>> The process that failed here is that it's anaconda's responsibility to change
>> this right now, but not our decision to decide when it should be changed. It
>> clearly belongs outside of anaconda, just like the yum repo files, release
>> notes, gpg keys, splash images, etc.
>
> ... should it even be *in* a package, as opposed to part of a buildstamp,
> or whatever?
I talked to clumens and jkeating for a bit about this on irc, and what we're
thinking right now is that if we're composing a tree that says it's
rawhide/development, then we write a .treeinfo that says to use betanag. Then
anaconda can check and see what treeinfo says and behave appropriately.
Jesse is going to check in to how feasible this is on the compose side.
--
Peter
Power corrupts. Absolute power is kind of neat.
-- John Lehman, Secretary of the Navy, 1981-1987
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
