On Thu, Oct 28, 2010 at 10:18:44AM +0200, Guillaume Rousse wrote: > Le 23/10/2010 19:40, Gonéri Le Bouder a écrit : > > On Wed, Oct 20, 2010 at 09:39:33PM +0200, Guillaume Rousse wrote: > >> Here is the issue with setup directory handling in the agent: > >> http://forge.fusioninventory.org/issues/273 > >> > >> I just made some radical changes in my branch to fix this issue, and > >> enhance the situation: > >> - basevardir and share-dir options don't exist anymore > > --basevardir was useful for the case the user was not allowed to write > > on the default directory. How do you deal with this situation now? > Anyway, that's indeed a problem if you run an *installed* agent with a > different user that's the one than installed it, and you can't switch > back to the installing user to make the directory writable by the second > user. In that case, you'd better just run the agent from its extraction > directory, or reinstall it with the second user. > > But is this scenario realistic enough to deserve a runtime option (by > opposition to an installation time one) ?Especially as we advice people > to run the agent as root users... Yes, I don't think so too
> >> - in the git tree, those values match local tree, so it just works,
> >> without the need for --devlib option
> > How do you detect when you are in the git tree?
> Because you run an unmodified executable.
Oh ok.
[...]
> Do we agree on that ?
ok
[...]
> I just took advantage of the post-installation process needed for first
> issue to implement this. And while just needing another substitution in
> Makefile.PL, it also make the agent code simpler.
So if understand, we have "just" to hack NSIS script so the install will
write a .pm file with the correct path after the installation.
/me runs :)
Best regards,
Gonéri Le bouder
signature.asc
Description: Digital signature
_______________________________________________ Fusioninventory-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/fusioninventory-devel
