687
edits
Changes
Jump to navigation
Jump to search
Line 27:
Line 27: + + + + + + + + +
Talk:Yum-plugin-priorities (view source)
Revision as of 16:43, 25 November 2008
, 16:43, 25 November 2008no edit summary
If you are only using two priority levels why not look at protectbase. It basically does the same thing and you only have to indicate which repos you want to protect <small>— [[User:Slords|Slords]] ([[User talk:Slords|talk]] • [[Special:Contributions/Slords|contribs]]).</small> 22:32, 24 November 2008 (UTC)
If you are only using two priority levels why not look at protectbase. It basically does the same thing and you only have to indicate which repos you want to protect <small>— [[User:Slords|Slords]] ([[User talk:Slords|talk]] • [[Special:Contributions/Slords|contribs]]).</small> 22:32, 24 November 2008 (UTC)
----
Is there a technical reason to prefer 'protectbase' over 'priorities'? If not, I'd prefer to stay with 'priorities' because, even though we're not advocating it for general use, it does have some more power for advanced users, or for future situations (I keep having ideas about this that turn out to be irrelevant when I start writing them down...)
I think 'priorities' is easier/safer since 'protectbase' defaults all non-specified repos to 'protected', while 'priorities' defaults non-specified repos to priority 99. If we use 'protectbase' we have to make sure all users set all custom repos to unprotected or else they will be protected, while with 'priorities' all custom repos default to the "correct" behavior.
I suppose this could be resolved by having the template expansion default repos to unprotected for any repo where "protect" is not set.
[[User:Mmccarn|Mmccarn]] 14:43, 25 November 2008 (UTC)