3 ms·

This behaviour is described on the home page [1]. Sorry it's not to your liking. fman's features are prioritised according to the number of votes they receive o

This behaviour is described on the home page [1]. Sorry it's not to your liking. fman's features are prioritised according to the number of votes they receive on a public Trello board [2]. There's a card for making it possible to disable automatic updates [3]. The intention is obviously not for it to come back when you delete it. If you remove it in the same way you installed it (via the package manager), then the files you mentioned are removed as well. [1]: https://fman.io/docs/obtaining-updates https://fman.io/docs/obtaining-updates [2]: https://trello.com/b/WpIUiPAd/fman https://trello.com/b/WpIUiPAd/fman [3]: https://trello.com/c/PZ664CEQ/9-make-auto-update-functionality-configurable https://trello.com/c/PZ664CEQ/9-make-auto-update-functionali...

pathsjs 10y ago
That is obviously not the home page. It is not even the first page when a user opens the documentation. Also, you make it sound like disabling automatic updates is something that requires work, hence needs to be prioritized on a task board. In fact it is quite the opposite: work was needed to enable automatic updates in the first place!
vog 10y ago
> This behaviour is described on the home page. This should be a big, fat warning with a clear description on how to install your package without the root cronjob. And that warning should appear right on the front site, not just some sub site. > Sorry it's not to your liking. This is not about personal taste. This is about violating well-established best practices that have very good reasons to exist. Running custom scripts as root, and especially adding custom cronjobs as root, should only be done if absolutely required for the tool to perform its task at all, e.g. for tools like logrotate. Everything else is a violation of trust, and thus a no-go for package maintainers. If a user wants daily updates, they configure the APT or Synaptic accordingly. It is the decision of the user, preferably for the whole system, at a time convenient for them. This is certainly not the decision of a single package maintainer. Keep in mind that many people choose a Free Software distribution like Debian because they developed an aversion to uninvited extra code running on their machine. Why? Because this is what was forced on them by their old proprietary operating system.
- mherrmann 10y ago
  Per your (and other people's) suggestion, I just released fman version 0.3.1 that removes the cron job. Again, I apologise. I did not know it was considered such a bad practice. I also wrote a blog post [1] that explains how to make sure that the cron job really has been removed. [1]: https://fman.io/blog/an-apology-to-linux-users/ https://fman.io/blog/an-apology-to-linux-users/
dflock 10y ago
I didn't mean that fman would come back. I meant that if I remove the cronjob and update script, the next time I get an fman update via my regularly scheduled update manager, fman's .deb installer will put the cronjob and script back.

pathsjs 10y ago

That is obviously not the home page. It is not even the first page when a user opens the documentation. Also, you make it sound like disabling automatic updates is something that requires work, hence needs to be prioritized on a task board. In fact it is quite the opposite: work was needed to enable automatic updates in the first place!

vog 10y ago

> This behaviour is described on the home page. This should be a big, fat warning with a clear description on how to install your package without the root cronjob. And that warning should appear right on the front site, not just some sub site. > Sorry it's not to your liking. This is not about personal taste. This is about violating well-established best practices that have very good reasons to exist. Running custom scripts as root, and especially adding custom cronjobs as root, should only be done if absolutely required for the tool to perform its task at all, e.g. for tools like logrotate. Everything else is a violation of trust, and thus a no-go for package maintainers. If a user wants daily updates, they configure the APT or Synaptic accordingly. It is the decision of the user, preferably for the whole system, at a time convenient for them. This is certainly not the decision of a single package maintainer. Keep in mind that many people choose a Free Software distribution like Debian because they developed an aversion to uninvited extra code running on their machine. Why? Because this is what was forced on them by their old proprietary operating system.

mherrmann 10y ago
Per your (and other people's) suggestion, I just released fman version 0.3.1 that removes the cron job. Again, I apologise. I did not know it was considered such a bad practice. I also wrote a blog post [1] that explains how to make sure that the cron job really has been removed. [1]: https://fman.io/blog/an-apology-to-linux-users/ https://fman.io/blog/an-apology-to-linux-users/

dflock 10y ago

I didn't mean that fman would come back. I meant that if I remove the cronjob and update script, the next time I get an fman update via my regularly scheduled update manager, fman's .deb installer will put the cronjob and script back.