Good morning.
I'm trying to build a module package but I'm running into issues with these macros. When I build in my FC9 development environment, I require init_script_file. When I use mock, it will only build using init_script_type. Why the difference, and what do I do about it?
While I might expect issues across versions, I don't expect a difference when my mock target and my build environment are the same.
Also, if FC10 is different from FC9, how do I handle that?
TIA - Dave
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
David Carter wrote:
Good morning.
I'm trying to build a module package but I'm running into issues with these macros. When I build in my FC9 development environment, I require init_script_file. When I use mock, it will only build using init_script_type. Why the difference, and what do I do about it?
While I might expect issues across versions, I don't expect a difference when my mock target and my build environment are the same.
Also, if FC10 is different from FC9, how do I handle that?
TIA
- Dave
-- fedora-selinux-list mailing list fedora-selinux-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-selinux-list
init_script_file is what you should use. That is what upstream wants.
This doesn't solve my problem of building on FC9 though...
On Oct 27, 2008, at 4:38 PM, Daniel J Walsh wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
David Carter wrote:
Good morning.
I'm trying to build a module package but I'm running into issues with these macros. When I build in my FC9 development environment, I require init_script_file. When I use mock, it will only build using init_script_type. Why the difference, and what do I do about it?
While I might expect issues across versions, I don't expect a difference when my mock target and my build environment are the same.
Also, if FC10 is different from FC9, how do I handle that?
TIA
- Dave
-- fedora-selinux-list mailing list fedora-selinux-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-selinux-list
init_script_file is what you should use. That is what upstream wants.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkkGEZ0ACgkQrlYvE4MpobNadgCgl2r7MXSlnl6JDSGjkGmAOF9d qaIAoKWgRaDHkiGBuKphhPrpD53FBp6A =QyPf -----END PGP SIGNATURE-----
selinux@lists.fedoraproject.org