Al 19/10/11 20:47, En/na brlcad ha escrit: > > On Oct 19, 2011, at 07:45 AM, Tom Browder <tom.brow...@gmail.com> wrote: > >> In looking at improving my packaging for the Debian standard (which >> uses the FHS), I see that perhaps I should be installing into the >> /opt/<package> hierarchy. Should not that be the case for BRL-CAD, >> too? > > So this is an old smelly can of worms, but I'll try to stay off the soapbox. > ;) > > For Debian, using /opt/brlcad/rel-VERSION would be a perfectly acceptable > multi-version installation prefix to use and fits within the constraints and > design of the FHS. It's a bit too SysV'ish for my taste, but it's their > guidelines for apt and reasonable enough in itself for their platform's > consistency. For a Debian *apt* description, that would be what I'd think > should be used. > > For .deb files we put up on Sourceforge or that you put together, however, > you can follow the FHS or whatever other convention suits our users. There's > just as strong an argument for following the FHS as there is for using our > historic path (since that's where any legacy BRL-CAD user has always been > told to look). If that's upsetting to new users expecting the FHS, they can > make their own .deb or they can work on getting proper apt integration > working. For now I leave that decision up to the binary platform maintainer > (Jordi) since they're the ones that will get assigned any support requests > related to the .deb they pull together. It comes down to making things > peculiar for new users or existing users. > > That said, I'm opposed to making /opt/brlcad our *project* default for the > some of the same reasons the FHS allows X11 in /usr. "An exception is made > for the X Window System because of considerable precedent and widely accepted > practice." The same can be said of BRL-CAD in /usr/brlcad .. and BRL-CAD has > been around using that path even longer than X11! For our own internally > distributed releases (the ones that go on Sourceforge), we should be > following the HACKING guidelines (i.e., /usr/brlcad/rel-VERSION). >
At first I tried to put it in /opt/ and I had some problems, now I do not remember what. Anyway I do not think that increases the chances of BRL-CAD to be added in the debian repository. Furthermore, I agree with Sean, so I'll keep as is at least by the moment. Regards, -- Jordi Sayol
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
