jheiss
commented
12 years ago And as a user pointed out, if tpkg were always running init scripts itself we could support an option in tpkg.xml to indicate what user to run the init script as, so that developers didn't have to deal with calling su themselves. I'm still not certain this is a good idea, as outside observers looking at the init script wouldn't see any indication about what user the script would run as, but the convenience for developers might be worth it.
Was: https://sourceforge.net/apps/trac/tpkg/ticket/14#comment:1
Currently several major tpkg features don't work if tpkg is not run as root, namely init scripts and crontabs. In both cases we currently hook into the related OS subsystem, which requires root privileges. Ideally these would be handled more like logrotate or stunnel where packages would express a dependency on a "cron" or "init" package and then drop crontabs or init scripts into /opt/tpkg/etc/cron.d or /opt/tpkg/etc/init.d and have them activated. The cron package could just run its own cron daemon and be completely independent of the OS cron system. This would eliminate the need for the
On the cron front I looked around at the available options and it seemed to me vixie-cron was the most appropriate, but it is a crufty old-school package that wasn't easily relocated to /opt/tpkg.
Was: https://sourceforge.net/apps/trac/tpkg/ticket/14