On 03/27/2013 08:54 PM, adrelanos wrote: > 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. I might sound silly, but ... what is /etc/environment for? What are the packages reading it, and for what use?
Thomas -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5153dc0c.4060...@debian.org
