Re: SELinux userspace patches in hardened-dev?
Luis Ressel <[email protected]>
| Newsgroups | gmane.linux.gentoo.hardened |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 6 Aug 2014 11:50:35 +0200 Amadeusz Sławiński <[email protected]> wrote: > On Tue, 5 Aug 2014 12:47:32 +0000 > Sven Vermeulen <[email protected]> wrote: > > > Hi all > > > > Is it ok if I create a branch in the hardened-dev repo (called > > "selinux-userland") which contains the patches for the various > > SELinux userland packages we maintain? > > > > Or would you prefer a different way to centrally manage the patches > > (they sometimes become too large to be put in the ${FILESDIR} so I > > moved towards a patchbundle)? > > > > Wkr, > > Sven Vermeulen > > > > Are these only patches or packages? > If only patches I think it's better to put them in separate > repository. Mainly because hardened-dev is used for portage tree > stuff and some other parts of hardened (proj/hardened-gccpatchset.git > proj/hardened-patchset.git) keep patches separately. > Perhaps hardened-selinuxpatchset? > > Amadeusz > > I'd rather not have to keep track of yet another repository. What's wrong with a branch? Using "git checkout --orphan newbranch", one can create completely independent branches. Regards, Luis ressel
signature.asc
(application/pgp-signature, 949 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJT4f7+XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBMjU3MDBFQTc5QkYzMkY4NEQzMTFGNDlD NzE4OTFBNkEwRUZCN0U5AAoJEMcYkaag77fpiDgP/RAFAkYdjHXB2cy/VEVhmKHV QrMcdGCdrbOSilspwS79oyrny7V2IGFY+IjIjFHLvZ6/ZH2ZGmW2anZ1t9IdYzlk Cbs61CzOkMtKBQ7Cd/0//RPeNyfS7KkJ5wPjJOPVxTumvGAN6oOq5Y0TvqHTpLN1 NnKQtUJNfjn6JFlHJ6E5KAm4O6gbpIiR5n/RiLCfNoyB+3nxrsRgoEwe5RYdkZ8J 2+/caFjzkA7jJf1HD8GNFepAyrLJCykfDZenxEKsQS/ABr6fsVO3dO4HzOMtGJF5 UoWwS65XLQ965KnEV1mpQ2SMruATrrp7leuutTT5UqyYFpqQT2ohdXlmqXJTc+9S OSbV+RnLLUWuD2dnEoecrVg6Lg4kDNLm7onp+QULEFt1x1xvDE2ha4sGtUF4TYNr W+MLMZY1FsMXXejrD24L62YdetKwfvjbDafoBLHz7cxj5BNhriZiATHe3fwWz4kg xmkKoWXiK5gpC5U68ARpovFFsT22sW933vkhhOO0UvC2vlH8hGjEZJ2c5b1uMDcf CNaxTKzRHMOWv4csypCrhv+nFH9TQdQlfUY3KVI7RTxIVPrJD3v7GHBTsaBYTysT 65DHKLzrzKVVrofKvI3YS0dqHIHvV+/36iQ4EAJYs42BOriKjoR/XQuODMbGV+LB o6nKU1RuZZS6TvvIDufK =F84D -----END PGP SIGNATURE-----