| 5 | | Specifically for the mimeset example cited, I'd say the preferred way is to create mime_db entries within home; e.g. for us ever since we've been shipping TT on Haiku PM we include a package that creates relative paths `data/mime_db/audio/aiff` ..etc with the mimeset-style attributes we need (Composer, Intro, Outro ..etc), saves me having to run the .sh script we had been using for a decade that calls setmime in extenso, very elegant and handy. Maybe there are other cases where writing files outside of the packagefs hierarchy can be replaced with another mechanism |
| | 5 | Specifically for the mimeset example cited, I'd say the preferred way is to create mime_db entries within home; e.g. for us ever since we've been shipping TT on Haiku PM we include a package that creates relative paths `data/mime_db/audio/aiff` ..etc with the mimeset-style attributes we need (Composer, Intro, Outro ..etc), saves me having to run the .sh script we had been using for a decade that calls setmime in extenso, very elegant and handy. Maybe there are other cases where writing files outside of the packagefs hierarchy can be replaced with another mechanism (EDIT: meant to say: writing in the global MIMEdb can be agreably replaced with writing to packagefs's config/data/mime_db, and probably there are other cases where it's not actually necessary to get non-packaged), as we'll probably want to keep that to a minimum.. Anyway for this one ticket, yea there are simpler ways to go, i'd rather keep this one low priority. |
