> -----Original Message----- > From: [email protected] [mailto:meego-packaging- > [email protected]] On Behalf Of Arjan van de Ven > Sent: Tuesday, June 21, 2011 3:42 PM > To: Brandt, Todd E > Cc: Ware, Ryan R; [email protected]; [email protected] > Subject: Re: [meego-packaging] meego-ux-mediafs spec fix > > > > %post > > /sbin/chkconfig --add meego-ux-mediafs if ! cat /etc/fuse.conf | grep > > -qw user_allow_other; then > > echo "user_allow_other">> /etc/fuse.conf fi > > this I'm not so sure about... > you add something, but never remove it
What requirement drives us to needing this option? Why would we not want to apply an access policy? We really want to give everyone a privilege that fuse by default only allows for root? If there is a real requirement for this I'll be happy to look at it and evaluate how we mitigate the additional security risk, but I'm not aware of any reason why we want the user to be able to mount filesystems without any access policy. > > %preun > > if [ -f /etc/init.d/meego-ux-mediafs ]; then > > /sbin/service meego-ux-mediafs stop> /dev/null 2>&1 || : > > /sbin/service meego-ux-mediafs restore> /dev/null 2>&1 || : > > fi > > /sbin/chkconfig --del meego-ux-mediafs > > I think this way will completely break software update > > %preun > if [ $1 -eq 0 ] ; then > /sbin/service<script> stop>/dev/null 2>&1 > /sbin/chkconfig --del<script> > fi > > > is the canonical way of doing this. > > %preun gets called during package update as well. I completely agree with this. I would be concerned about software updates breaking if we accepted it. It should definitely use the standard %preun. Ryan _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
