<blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"><span class="gmail_quote">On 16/10/2007, <b class="gmail_sendername">Karel Zak</b> <<a href="mailto:kzak@redhat.com">
kzak@redhat.com</a>> wrote:</span>On Tue, Oct 16, 2007 at 11:12:48AM +0200, Tomas Mraz wrote:<br>><br>> On Tue, 2007-10-16 at 10:59 +0200, Lubomir Kundrak wrote:<br>> > On Mon, 2007-10-15 at 23:31 +0200, Karel Zak wrote:
<br>> > > Couldn't be better to maintain default selinux labels like others<br>> > > file attributes?<br>> > ><br>> > > %attr(4755,root,root) %selinux(foo_t) /bin/foo<br><br>
we have more policies, so probably:<br><br> %selinux(policynameA, context_t), %selinux(policynameB, context_t),<br></blockquote><br>I'm not mad keen on having to do these kind of actions in spec files. This does not scale well.
<br><br><div><span class="gmail_quote">On 16/10/2007, <b class="gmail_sendername">Gianluca Sforna</b> <<a href="mailto:giallu@gmail.com">giallu@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 10/16/07, Tomas Mraz <<a href="mailto:tmraz@redhat.com">tmraz@redhat.com</a>> wrote:<br>><br>> On Tue, 2007-10-16 at 10:59 +0200, Lubomir Kundrak wrote:<br>> ><br>> > I was thinking many times why don't we already do it this way. Much more
<br>> > elegant and maintainable than restorecon in scriptlets.<br>> And how does that take care of updating file_contexts so the labels are<br>> not lost on the next filesystem relabel? This only means that the
<br>> initial labelling information is duplicated on two places and that<br>> doesn't seem to me like a good idea.<br><br>Also, I'm sure you don't want Joe sub-average packager (that is... me)<br>to mess around with SELinux contexts...
</blockquote><div><br>I don't want to mess around with SELinux contexts. Can't this be made part of %post or something? Speaking as an amateur I'm really not in favour of an additional piece of work that has to be added to the spec. Documenting another change is ... not great.
<br></div><br></div>Cheers<br>Chris<br clear="all"><br>-- <br><a href="http://www.chruz.com">http://www.chruz.com</a>