[maemo-developers] Considering /opt and MyDocs in your packages
From: Andrew Flegg andrew at bleb.orgDate: Thu Oct 22 00:09:16 EEST 2009
- Previous message: Considering /opt and MyDocs in your packages
- Next message: Considering /opt and MyDocs in your packages
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Oct 21, 2009 at 21:43, Martin Grimme <martin.grimme at gmail.com> wrote: > > in my opinion, maemo-optify shouldn't be hailed as the > good-for-everyone savior to the rootfs space issue. I see it as a > workaround for software that cannot be easily relocated to /opt. Agreed. Software which is written specifically (or, primarily) for Maemo can be designed to either be relocatable, or installed into /opt/<package>. This separates maemo-optify stuff (/opt/maemo/<path>) from the more specific /opt/<package>. See, for example: * Bounce * Classic Gaming Wallpapers * Hermes * mClock (uses /opt/<vendor>/<package>, which is also allowed under FHS) > Please don't get me wrong. optify is still useful and good to have, > but everybody should bear in mind that it's only a workaround, and > that relocating the software to /opt would be a much safer and more > elegant solution. > IMHO optify is OK for porting software from upstream, but if you write > specifically for the N900, you should rather consider making your > software easily relocatable eventually. Hear hear! Cheers, Andrew -- Andrew Flegg -- mailto:andrew at bleb.org | http://www.bleb.org/
- Previous message: Considering /opt and MyDocs in your packages
- Next message: Considering /opt and MyDocs in your packages
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]