[aur-general] OneSwarm in AUR wants to update itself
Hi,
I just created a package for OneSwarm [1] and uploaded it to the AUR [2]. The package works fine except that it has an auto-update feature, which of course doesn't work since the user does not have write access to /opt/OneSwarm. What is the correct way of dealing with this? Should I make /opt/OneSwarm writable by the users group?
Thanks,
Mathias
On Sat, Apr 4, 2009 at 20:05, Mathias Burén mathias.buren@gmail.com wrote:
Hi,
I just created a package for OneSwarm [1] and uploaded it to the AUR [2]. The package works fine except that it has an auto-update feature, which of course doesn't work since the user does not have write access to /opt/OneSwarm. What is the correct way of dealing with this? Should I make /opt/OneSwarm writable by the users group?
Thanks,
Mathias
Is there a way to disable this feature?
Yes, once you installed and started the program, you should be able to find the settings somewhere. But again, these are per-user settings. If you don't disable the auto update feature you get a popup every 20 minutes or so saying there's an update (yes, even though the program from the website is up to date, I don't know why it wants to update anyway).
Mathias
2009/4/5 Daenyth Blank <daenyth+arch@gmail.com daenyth%2Barch@gmail.com>
On Sat, Apr 4, 2009 at 20:05, Mathias Burén mathias.buren@gmail.com wrote:
Hi,
I just created a package for OneSwarm [1] and uploaded it to the AUR [2]. The package works fine except that it has an auto-update feature, which
of
course doesn't work since the user does not have write access to /opt/OneSwarm. What is the correct way of dealing with this? Should I
make
/opt/OneSwarm writable by the users group?
Thanks,
Mathias
Is there a way to disable this feature?
Mathias Burén wrote:
Yes, once you installed and started the program, you should be able to find the settings somewhere. But again, these are per-user settings. If you don't disable the auto update feature you get a popup every 20 minutes or so saying there's an update (yes, even though the program from the website is up to date, I don't know why it wants to update anyway).
Mathias
If any other distros have this packaged, they probably have a patch to disable this. I'd check them out.
Allan
On Sat, Apr 4, 2009 at 20:27, Allan McRae allan@archlinux.org wrote:
Mathias Burén wrote:
Yes, once you installed and started the program, you should be able to find the settings somewhere. But again, these are per-user settings. If you don't disable the auto update feature you get a popup every 20 minutes or so saying there's an update (yes, even though the program from the website is up to date, I don't know why it wants to update anyway).
Mathias
If any other distros have this packaged, they probably have a patch to disable this. I'd check them out.
Allan
Agreed, patching it out seems the way to go if the software is that stupid
On Sun, 5 Apr 2009 01:05:59 +0100 Mathias Burén mathias.buren@gmail.com wrote:
Hi,
I just created a package for OneSwarm [1] and uploaded it to the AUR [2]. The package works fine except that it has an auto-update feature, which of course doesn't work since the user does not have write access to /opt/OneSwarm. What is the correct way of dealing with this? Should I make /opt/OneSwarm writable by the users group?
Thanks,
Mathias
Is there any way to run the update within the fakeroot inside the build function? Disabling updates which aren't included in the latest source doesn't seem like an ideal solution.
Also, is it necessary to have 'j2re' in the depends array? This currently prevents it from working with openjdk6... I'm not sure if this is due to an error in the provides line of jre (j2re, java-runtime=6) or openjdk (java-environment=6, java-runtime=6) or due to real incompatibility.
Mathias Burén schrieb:
Hi,
I just created a package for OneSwarm [1] and uploaded it to the AUR [2]. The package works fine except that it has an auto-update feature, which of course doesn't work since the user does not have write access to /opt/OneSwarm. What is the correct way of dealing with this? Should I make /opt/OneSwarm writable by the users group?
Thanks,
Mathias
Hello,
your package relies on the binary tarballs from upstream. Did you try to build from the sources?
There may be more possibilities to influence the behaviour using that level.
Regards Stefan
Hi,
Thanks for all the inputs. I'll try to incorporate them. Yes, it sadly relies on binaries, but building it is very difficult it seems at the moment [1] but I'll try later on.
Regards,
Mathias
[1] http://forum.oneswarm.org/topic/58
2009/4/5 Stefan Husmann stefan-husmann@t-online.de
Mathias Burén schrieb:
Hi,
I just created a package for OneSwarm [1] and uploaded it to the AUR [2]. The package works fine except that it has an auto-update feature, which of course doesn't work since the user does not have write access to /opt/OneSwarm. What is the correct way of dealing with this? Should I make /opt/OneSwarm writable by the users group?
Thanks,
Mathias
Hello,
your package relies on the binary tarballs from upstream. Did you try to build from the sources?
There may be more possibilities to influence the behaviour using that level.
Regards Stefan
participants (5)
-
Allan McRae
-
Daenyth Blank
-
Mathias Burén
-
Stefan Husmann
-
xyne