if the file is program data which is only read, newver written, then linking to a common location e. /usr/share/appname/datafile is the most efficient, especially for large datafiles (think warzone2100 for example).  I haven't seen any good way of handling this in a slackbuild, because you may have many existing users, and what about users added later?. editing the default user template to add link creation and going through existing users to add links is not ideal. if you remove the package, the links will remain.

It is better if possible to get upstream to fix their code so that common user data is stored in a common place. local user data should be created as required by the software.
regards,
Tim

On 21/04/2021 03:06, slackbui...@ninefamily.com wrote:
If an application needs to use a file in the user's /home what is the correct way to do so in a Slackbuild?  Do I put it in a central place and link to it or just instruct the user to manually put the file or a script for it?

Thanks

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



--
This email has been checked for viruses by AVG.
https://www.avg.com

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to