On Mon, Jan 28, 2002 at 05:49:00PM -0500, Charles Wilson wrote: >Michael A Chase wrote: > >>Shouldn't this be part of the ash package? Now that it's part of the Base >>category, there shouldn't be any problem creating /etc/profile when ash is >>installed. > > >No. ash provides ash. base-files provides the data for a purely >data-driven setup.exe. That is, the scripts (which require ash) to >create /etc/.profile, /etc/.bashrc, etc. > >base-files may later do more stuff, like create the /usr/local/ tree and >the /var tree -- why should setup.exe have that stuff hardcoded into it? > >Once the configuration tasks performed by base-files grows, why should >it be part of the "ash" package? You don't want to redo the setup >scripts when updating ash.exe, do you?
No, but there's no reason why installation of 'sed' should cause the creation of /etc/profile either. I don't see any reason why this functionality couldn't either be part of ash/bash installation (although the /etc/profile that gets created isn't really ash-aware) with some intelligence for not overwriting the profile file. Either that or we make the base-files package more intelligent about what it installs and when. That's doable. cgf
