Is it considered less safe, or is there another reason that the default createrepo_flags for repositories include "-c cache" but not "--update"? Using --update cuts my reposync time dramatically for RHEL5 update channels, and I'd imagine that most users would derive similar benefit.
Ian Ward Comfort wrote:
Is it considered less safe, or is there another reason that the default createrepo_flags for repositories include "-c cache" but not "--update"? Using --update cuts my reposync time dramatically for RHEL5 update channels, and I'd imagine that most users would derive similar benefit.
No reason at all, that seems like a wise improvement (need to do a quick check to make sure that option is available on EL4 to see if we need to code around that, but shouldn't be).
--Michael
On 23 Apr 2009, at 2:16 PM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
Is it considered less safe, or is there another reason that the default createrepo_flags for repositories include "-c cache" but not "--update"? Using --update cuts my reposync time dramatically for RHEL5 update channels, and I'd imagine that most users would derive similar benefit.
No reason at all, that seems like a wise improvement (need to do a quick check to make sure that option is available on EL4 to see if we need to code around that, but shouldn't be).
Right, good point. It looks like EPEL packages createrepo 0.4.3 for EL4, and --update didn't appear until 0.4.10. (Is EPEL what most people use?)
Ian Ward Comfort wrote:
On 23 Apr 2009, at 2:16 PM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
Is it considered less safe, or is there another reason that the default createrepo_flags for repositories include "-c cache" but not "--update"? Using --update cuts my reposync time dramatically for RHEL5 update channels, and I'd imagine that most users would derive similar benefit.
No reason at all, that seems like a wise improvement (need to do a quick check to make sure that option is available on EL4 to see if we need to code around that, but shouldn't be).
Right, good point. It looks like EPEL packages createrepo 0.4.3 for EL4, and --update didn't appear until 0.4.10. (Is EPEL what most people use?)
RHEL4 users usually get yum from there, yes. We could make the cobbler check code look for that as well, though it might just be easier to suggest people add that in the settings file comments (and mention what version it appears in).
--Michael
On 24 Apr 2009, at 5:16 AM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
On 23 Apr 2009, at 2:16 PM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
Is it considered less safe, or is there another reason that the default createrepo_flags for repositories include "-c cache" but not "--update"? Using --update cuts my reposync time dramatically for RHEL5 update channels, and I'd imagine that most users would derive similar benefit.
No reason at all, that seems like a wise improvement (need to do a quick check to make sure that option is available on EL4 to see if we need to code around that, but shouldn't be).
Right, good point. It looks like EPEL packages createrepo 0.4.3 for EL4, and --update didn't appear until 0.4.10. (Is EPEL what most people use?)
RHEL4 users usually get yum from there, yes. We could make the cobbler check code look for that as well, though it might just be easier to suggest people add that in the settings file comments (and mention what version it appears in).
Is there a natural place for this in the settings file that I'm missing? The default createrepo flags are currently hardcoded in item_repo.py, though it would be easy enough to move this to a yumcreaterepo_flags setting and recommend, say, "-c cache --update -C" to users with createrepo >= 0.4.10.
Ian Ward Comfort wrote:
On 24 Apr 2009, at 5:16 AM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
On 23 Apr 2009, at 2:16 PM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
Is it considered less safe, or is there another reason that the default createrepo_flags for repositories include "-c cache" but not "--update"? Using --update cuts my reposync time dramatically for RHEL5 update channels, and I'd imagine that most users would derive similar benefit.
No reason at all, that seems like a wise improvement (need to do a quick check to make sure that option is available on EL4 to see if we need to code around that, but shouldn't be).
Right, good point. It looks like EPEL packages createrepo 0.4.3 for EL4, and --update didn't appear until 0.4.10. (Is EPEL what most people use?)
RHEL4 users usually get yum from there, yes. We could make the cobbler check code look for that as well, though it might just be easier to suggest people add that in the settings file comments (and mention what version it appears in).
Is there a natural place for this in the settings file that I'm missing? The default createrepo flags are currently hardcoded in item_repo.py, though it would be easy enough to move this to a yumcreaterepo_flags setting and recommend, say, "-c cache --update -C" to users with createrepo >= 0.4.10.
I must be thinking of reposync flags.
We should put this into settings too.
--Michael
On 24 Apr 2009, at 4:33 PM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
On 24 Apr 2009, at 5:16 AM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
On 23 Apr 2009, at 2:16 PM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
Is it considered less safe, or is there another reason that the default createrepo_flags for repositories include "-c cache" but not "--update"? Using --update cuts my reposync time dramatically for RHEL5 update channels, and I'd imagine that most users would derive similar benefit.
No reason at all, that seems like a wise improvement (need to do a quick check to make sure that option is available on EL4 to see if we need to code around that, but shouldn't be).
Right, good point. It looks like EPEL packages createrepo 0.4.3 for EL4, and --update didn't appear until 0.4.10. (Is EPEL what most people use?)
RHEL4 users usually get yum from there, yes. We could make the cobbler check code look for that as well, though it might just be easier to suggest people add that in the settings file comments (and mention what version it appears in).
Is there a natural place for this in the settings file that I'm missing? The default createrepo flags are currently hardcoded in item_repo.py, though it would be easy enough to move this to a yumcreaterepo_flags setting and recommend, say, "-c cache --update - C" to users with createrepo >= 0.4.10.
I must be thinking of reposync flags.
We should put this into settings too.
I've got a small patch for this, if the name yumcreaterepo_flags is OK (like yumreposync_flags -- or I could change it).
Ian Ward Comfort wrote:
On 24 Apr 2009, at 4:33 PM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
On 24 Apr 2009, at 5:16 AM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
On 23 Apr 2009, at 2:16 PM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
> Is it considered less safe, or is there another reason that the > default createrepo_flags for repositories include "-c cache" > but not "--update"? Using --update cuts my reposync time > dramatically for RHEL5 update channels, and I'd imagine that > most users would derive similar benefit. > No reason at all, that seems like a wise improvement (need to do a quick check to make sure that option is available on EL4 to see if we need to code around that, but shouldn't be).
Right, good point. It looks like EPEL packages createrepo 0.4.3 for EL4, and --update didn't appear until 0.4.10. (Is EPEL what most people use?)
RHEL4 users usually get yum from there, yes. We could make the cobbler check code look for that as well, though it might just be easier to suggest people add that in the settings file comments (and mention what version it appears in).
Is there a natural place for this in the settings file that I'm missing? The default createrepo flags are currently hardcoded in item_repo.py, though it would be easy enough to move this to a yumcreaterepo_flags setting and recommend, say, "-c cache --update - C" to users with createrepo >= 0.4.10.
I must be thinking of reposync flags.
We should put this into settings too.
I've got a small patch for this, if the name yumcreaterepo_flags is OK (like yumreposync_flags -- or I could change it).
That works well.
--Michael
On 27 Apr 2009, at 8:50 AM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
On 24 Apr 2009, at 4:33 PM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
On 24 Apr 2009, at 5:16 AM, Michael DeHaan wrote:
Ian Ward Comfort wrote:
On 23 Apr 2009, at 2:16 PM, Michael DeHaan wrote: > Ian Ward Comfort wrote: >> Is it considered less safe, or is there another reason that >> the default createrepo_flags for repositories include "-c >> cache" but not "--update"? Using --update cuts my reposync >> time dramatically for RHEL5 update channels, and I'd imagine >> that most users would derive similar benefit.
> > No reason at all, that seems like a wise improvement (need to > do a quick check to make sure that option is available on EL4 > to see if we need to code around that, but shouldn't be).
Right, good point. It looks like EPEL packages createrepo 0.4.3 for EL4, and --update didn't appear until 0.4.10. (Is EPEL what most people use?)
RHEL4 users usually get yum from there, yes. We could make the cobbler check code look for that as well, though it might just be easier to suggest people add that in the settings file comments (and mention what version it appears in).
Is there a natural place for this in the settings file that I'm missing? The default createrepo flags are currently hardcoded in item_repo.py, though it would be easy enough to move this to a yumcreaterepo_flags setting and recommend, say, "-c cache -- update -C" to users with createrepo >= 0.4.10.
I must be thinking of reposync flags.
We should put this into settings too.
I've got a small patch for this, if the name yumcreaterepo_flags is OK (like yumreposync_flags -- or I could change it).
That works well.
Here it is.
I must be thinking of reposync flags.
We should put this into settings too.
I've got a small patch for this, if the name yumcreaterepo_flags is OK (like yumreposync_flags -- or I could change it).
That works well.
Here it is.
cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
Applied, thanks!
cobbler-devel@lists.fedorahosted.org
-
Ian Ward Comfort -
Michael DeHaan