Martin Steigerwald - 11.05.19, 11:26: > Hi. > > Now that the proof of concept is out, I am thinking about extending it > a little bit. > > - make is a package > - make "install-or-update.sh" into "/usr/bin/userservices" with the > following actions: > - install: Sets up userservices for the user > - update: Updates it > - remove: Removes i
- remove: Removes user services from user directory completely (after confirmation) Okay, while discussing this with Evilham, I agree that there likely is no need to differentiate between "install" and "update". I bet that is why I started with "install-or-update.sh" to begin with. Keep it stateless, keep it simple. As only > - make "userservice" alias into "/usr/bin/userservice" > - that way the user would not have to setup an alias anymore. will adapt the symlinks that are in ~/$SERVICEDIR/enabled (SERVICEDIR=".service" by default) and that on user request only. If one really likes to overwrite own changes to "run" files, there can be an "--overwrite" option. > So with these changes using user services would be like: > > As root: > > apt install user-services > > As user: > > userservices install > > userservice enable redshift > > [x] done :) > > > If user-services packaged gets updated, the user can decide to update > her installation with: > > userservices update > > Ideally it would take into account when the user changed some > services. > > > What do you think about that? > > It would be some work, but I for me this sounds like a good idea. > > > In anyway: This is still in proof of concept stage, so I may change > everything :). If you are using this, you are brave alpha tester :) Thanks, -- Martin _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
