Re: Another possible slink goal (multipackages users profile)
Joey Hess wrote:
> I think you're on the right track here.
Thanks. :-)
> Martin Schulze wrote:
> > . All programs that use env-add / env-remove have to call update-env
> > (maybe it should consitantly be called env-update) in their postinst
> > and it uses the same mechanism like update-menus in order to not
> > run in 10 instances.
>
> I disagree with this. The real reason update-menus backgrounds itself and
> runs after dpkg is that it needs to be able to see what the dpkg status file
> looks like after dpkg is done installing packages. Update-env doesn't need
> this, so it shouldn't use this complicated and error-prone mechanism.
I'd like to see it here for exactly the same reason.
Why doen't update-menus work at once? Because during a new installation
it'll re-create all the files 50 times, at every invocation. The same
applies to update-env. Since it won't be called more than 10 time this
is not so important but still takes time which is not needed.
> > . All shells must know a mechanism to read and parse /etc/env and
>
> And I disargee with this. Requiring all shells be specially modified is bad.
> Rather, I think update-env should generate /etc/env.bash, /etc/env.csh, etc,
> and shells should simply souce those files.
Whoops, now I know why this sentence didn't end. It ought to be removed.
It's not needed if update-env modifies /etc/profile, /etc/cshrc &c.
Sorry,
Joey
--
VFS: no free i-nodes, contact Linus -- finlandia, Feb '94
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: