The pungi in git is clearly for Fedora. It can however be used for RHEL 7 but a few "patches" are needed for it to work.
How would the patches best be put in pungi? There can be individual command line options added that enable/disable features. A example of this is there is no hfs support in RHEL 7 so a "nomacboot" command line option could be added to disable this. Another option is a single "rhel7" option that could cover all the rhel 7 patches. Which way would be best?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 18 Dec 2014 10:20:50 -0600 Connie Sieh csieh@fnal.gov wrote:
The pungi in git is clearly for Fedora. It can however be used for RHEL 7 but a few "patches" are needed for it to work.
How would the patches best be put in pungi? There can be individual command line options added that enable/disable features. A example of this is there is no hfs support in RHEL 7 so a "nomacboot" command line option could be added to disable this. Another option is a single "rhel7" option that could cover all the rhel 7 patches. Which way would be best?
The best way would be to add flags for the individual features.
Dennis
On Thu, 18 Dec 2014, Dennis Gilmore wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 18 Dec 2014 10:20:50 -0600 Connie Sieh csieh@fnal.gov wrote:
The pungi in git is clearly for Fedora. It can however be used for RHEL 7 but a few "patches" are needed for it to work.
How would the patches best be put in pungi? There can be individual command line options added that enable/disable features. A example of this is there is no hfs support in RHEL 7 so a "nomacboot" command line option could be added to disable this. Another option is a single "rhel7" option that could cover all the rhel 7 patches. Which way would be best?
The best way would be to add flags for the individual features.
Dennis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
I have attached a patch for pungi 3.12.1 that provides a option "nomacboot". This command line option tells pungi to not include macboot in the compose. This is needed for EL7 as it does not provide HFS. The default has not been changed.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, 22 Dec 2014 14:14:15 -0600 Connie Sieh csieh@fnal.gov wrote:
On Thu, 18 Dec 2014, Dennis Gilmore wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 18 Dec 2014 10:20:50 -0600 Connie Sieh csieh@fnal.gov wrote:
The pungi in git is clearly for Fedora. It can however be used for RHEL 7 but a few "patches" are needed for it to work.
How would the patches best be put in pungi? There can be individual command line options added that enable/disable features. A example of this is there is no hfs support in RHEL 7 so a "nomacboot" command line option could be added to disable this. Another option is a single "rhel7" option that could cover all the rhel 7 patches. Which way would be best?
The best way would be to add flags for the individual features.
Dennis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
I have attached a patch for pungi 3.12.1 that provides a option "nomacboot". This command line option tells pungi to not include macboot in the compose. This is needed for EL7 as it does not provide HFS. The default has not been changed.
Thanks,
I have pulled it into the newly created epel7 branch as well as master
Dennis
On 18 December 2014 at 09:20, Connie Sieh csieh@fnal.gov wrote:
The pungi in git is clearly for Fedora. It can however be used for RHEL 7 but a few "patches" are needed for it to work.
How would the patches best be put in pungi? There can be individual command line options added that enable/disable features. A example of this is there is no hfs support in RHEL 7 so a "nomacboot" command line option could be added to disable this. Another option is a single "rhel7" option that could cover all the rhel 7 patches. Which way would be best?
Should we branch this version or patches for it into EPEL for EL7 or earlier versions?
-- Connie J. Sieh Computing Services Specialist III
Fermi National Accelerator Laboratory 630 840 8531 office
http://www.fnal.gov csieh@fnal.gov -- buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys
buildsys@lists.fedoraproject.org