Tom Brown wrote:
If you want to maintain your own repo with rpms, all you have to do
is ...
mkdir /opt/foo
cp <lots of rpms> /opt/foo
cobbler repo add --name=foo-name --mirror=/opt/foo
(this actually uses rsync, so if you have another box in your org,
with a directory full of RPMs, you can pass in
--mirror=user@server:/opt/foo)
And it will take care of calling createrepo and making sure the repo
config files are all created correctly.
I'd recommend doing that rather than trying to add an RPM to an
existing mirrored repo, as that will make it clearer what comes from
where and you can enable/disable individual repos as needed.
thanks - i will bear this in mind - for this scenario i just added
that rpm to a current repo - ram createrepo on it and then cobbler
reposync and thats now available in the repo cobbler is aware of. I
will add and remove rpm's from existing repo's quite a lot so creating
a repo each time would be a bit of a pain to manage.
Right, use the above trick and it will be dealt with automatically, if
you add it to an existing one, reposync will undo your changes each time
you update.
thanks
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
