This is not abit issue just a minor annoyance.
I use Foreman to provision my systems and to keep control I remove all the default *.repo files andkeep away from installing more *.repo files so I can control the content via the foreman(katello) provided redhat.repo.
I would argue that the *-release-*.rpm should not contain any setup code but just the stuff in /etc/yum.repos.d.
Maybe you just don't need to remove anything at all but just move them to another folder that does the same goal. For *-release-*.rpm, again it is explained itself.
Xlord
-----Original Message----- From: CentOS-virt [mailto:centos-virt-bounces@centos.org] On Behalf Of Alvin Starr Sent: Tuesday, March 21, 2017 1:45 AM To: centos-virt@centos.org Subject: [CentOS-virt] grub-bootxen.sh
This is not abit issue just a minor annoyance.
I use Foreman to provision my systems and to keep control I remove all the default *.repo files andkeep away from installing more *.repo files so I can control the content via the foreman(katello) provided redhat.repo.
I would argue that the *-release-*.rpm should not contain any setup code but just the stuff in /etc/yum.repos.d.
I actually move the default *.repo files and replace them with "".
The thing is that Katello turns all the downloaded yum content into a single redhat.repo file and I don't have to install any more *-release-* rpms any more.
I would argue that I should not need to install any *-release-* rpms at all to get all the required software.
On 03/22/2017 09:34 AM, -=X.L.O.R.D=- wrote:
Maybe you just don't need to remove anything at all but just move them to another folder that does the same goal. For *-release-*.rpm, again it is explained itself.
Xlord
-----Original Message----- From: CentOS-virt [mailto:centos-virt-bounces@centos.org] On Behalf Of Alvin Starr Sent: Tuesday, March 21, 2017 1:45 AM To: centos-virt@centos.org Subject: [CentOS-virt] grub-bootxen.sh
This is not abit issue just a minor annoyance.
I use Foreman to provision my systems and to keep control I remove all the default *.repo files andkeep away from installing more *.repo files so I can control the content via the foreman(katello) provided redhat.repo.
I would argue that the *-release-*.rpm should not contain any setup code but just the stuff in /etc/yum.repos.d.
On 03/22/2017 09:35 AM, Alvin Starr wrote:
I actually move the default *.repo files and replace them with "".
The thing is that Katello turns all the downloaded yum content into a single redhat.repo file and I don't have to install any more *-release-* rpms any more.
I would argue that I should not need to install any *-release-* rpms at all to get all the required software.
The reason it exists that way is to allow you to not get duplicate kernel entries. If we don't get the script installed before you get the kernel, then you get a normal kernel entry, then later a xen kernel entry.
On 03/22/2017 09:34 AM, -=X.L.O.R.D=- wrote:
Maybe you just don't need to remove anything at all but just move them to another folder that does the same goal. For *-release-*.rpm, again it is explained itself.
Xlord
-----Original Message----- From: CentOS-virt [mailto:centos-virt-bounces@centos.org] On Behalf Of Alvin Starr Sent: Tuesday, March 21, 2017 1:45 AM To: centos-virt@centos.org Subject: [CentOS-virt] grub-bootxen.sh
This is not abit issue just a minor annoyance.
I use Foreman to provision my systems and to keep control I remove all the default *.repo files andkeep away from installing more *.repo files so I can control the content via the foreman(katello) provided redhat.repo.
I would argue that the *-release-*.rpm should not contain any setup code but just the stuff in /etc/yum.repos.d.
On 03/24/2017 03:29 PM, Johnny Hughes wrote:
On 03/22/2017 09:35 AM, Alvin Starr wrote:
I actually move the default *.repo files and replace them with "".
The thing is that Katello turns all the downloaded yum content into a single redhat.repo file and I don't have to install any more *-release-* rpms any more.
I would argue that I should not need to install any *-release-* rpms at all to get all the required software.
The reason it exists that way is to allow you to not get duplicate kernel entries. If we don't get the script installed before you get the kernel, then you get a normal kernel entry, then later a xen kernel entry.
OK. That makes sense.
I wonder if there is some other way to handle this.
It looks like that it may be possible to use "OrderWithRequires" in the RPMS that need the grub-bootxen.sh.
I will try to poke at this a bit more.
On 03/22/2017 09:34 AM, -=X.L.O.R.D=- wrote:
Maybe you just don't need to remove anything at all but just move them to another folder that does the same goal. For *-release-*.rpm, again it is explained itself.
Xlord
-----Original Message----- From: CentOS-virt [mailto:centos-virt-bounces@centos.org] On Behalf Of Alvin Starr Sent: Tuesday, March 21, 2017 1:45 AM To: centos-virt@centos.org Subject: [CentOS-virt] grub-bootxen.sh
This is not abit issue just a minor annoyance.
I use Foreman to provision my systems and to keep control I remove all the default *.repo files andkeep away from installing more *.repo files so I can control the content via the foreman(katello) provided redhat.repo.
I would argue that the *-release-*.rpm should not contain any setup code but just the stuff in /etc/yum.repos.d.
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
-
-=X.L.O.R.D=- -
Alvin Starr -
Johnny Hughes