Request For Candidates: Application Review Board

[Stephan Hermann]

On Thu, Aug 26, 2010 at 09:41:00AM -0700, Steve Langasek wrote:
> On Thu, Aug 26, 2010 at 12:00:59PM -0400, James Westby wrote:
> > No, as I understand it, it is a .deb, but without maintainer scripts
> > (with triggers to take care of things, rather than arbitary code), and
> > any other restriction that we wish to place, such as no /etc/cron*
> > files. (I'm not sure I agree with pitti that we should go outside the
> > standard FHS here, but it does have a nice fail-closed property.)
> 
> I wouldn't say this is going outside the FHS.  /opt is defnitely *part* of
> the FHS... it's the heirarchy reserved for packages from third-party vendors
> (as distinct from the OS vendor), which in a sense is precisely what these
> are.  So to me, this seems an altogether proper place for them.

AFAIK is /opt right now not under control of any package we have.
/opt will be created in a maintainer script from base-files pkg.
and it can be easily removed from a package which uses /opt as prefix by accident.

so you can remove it and base-files won't bother to re-create it.

from base-files/debian/FAQ:
Q. I upgraded from woody to sarge. Should my system be FHS-compliant now?                                                                                                                                        
                                                                                                                                                                                                                 
A. Achieving FHS compliance by upgrading would be tricky and prone to                                                                                                                                            
error in certain cases, so it is not a goal of base-files, nor it is                                                                                                                                             
planned to be. By default, some "mandatory" directories (like /opt,                                                                                                                                              
/srv or /media) are only created in the first install (performed by                                                                                                                                              
debootstrap), to keep the code as simple as possible, follow the                                                                                                                                                 
principle of least surprise on upgrades, and also to give people the                                                                                                                                             
freedom to remove those directories without them being created again                                                                                                                                             
when base-files is upgraded. Therefore, if you are running any sort of                                                                                                                                           
compliance tests, you should do it on newly installed systems only.                   

Regards,

\sh


> -- 
> ubuntu-devel mailing list
> ubuntu-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20100827/d1204acc/attachment.pgp