[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#704054: marked as done (/etc/environment.d)



Your message dated Thu, 28 Mar 2013 19:02:03 +0100
with message-id <201303281902.04274.holger@layer-acht.org>
and subject line Re: Bug#704054: /etc/environment.d
has caused the Debian Bug report #704054,
regarding /etc/environment.d
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
704054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704054
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: wishlist

I'd like to have a /etc/environment.d folder. Contributing that code
shouldn't be hard for me. But I don't know where the would be the best
place to implement it and how?

http://codesearch.debian.net tells, that many packages read
/etc/environment directly, not using some system mechanism to get the
contents of it, which makes the implementation harder.

Asking all affected packages to read /etc/environment.d as well or to
start using a system function to do that seems unlikely?

The most realistic option could be to write something similar to
resolvconf, i.e. creating a package which phrases /etc/environment.d
and dynamically creates /etc/environment.

Please tell me what you think.

--- End Message ---
--- Begin Message ---
Hi,

On Donnerstag, 28. März 2013, adrelanos wrote:
> Lars Wirzenius:
> > On Wed, Mar 27, 2013 at 10:36:44AM -0700, Steve Langasek wrote:
> > Now that the specific technical change has been opposed: adrelanos, could
> > you describe the actual problem you wanted to solve with
> > /etc/environment.d? Perhaps there is a better solution we can suggest
> > for that.
> Thanks, I can think of other solutions, it's just that I find this .d
> structure really clean, beautiful and simple to use.

since we haven't heard yet of a use-case for the proposed solution and as the 
pam maintainers have disagreed with the solution too, I'm closing this bug.


cheers,
	Holger

--- End Message ---

Reply to: