On Thu, 6 Mar 2003 15:30:01 -0500 Tyler Trafford <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 06, 2003 at 03:04:29PM -0500, Ian Truelsen wrote: > > On Thu, 6 Mar 2003 11:31:23 -0800 > > Balaji Srinivasan <[EMAIL PROTECTED]> wrote: > > > > > One way these conflicts could be reduced is by separating out > > > sections in config files that will most probably be modified by > > > the user and those which are not. For example the USE directive > > > and the CFLAGS directive from make.conf could be moved to a > > > separate file. That way whenever portage changes, they wouldnt > > > need to update those flags (or even if they did it would be easy > > > to merge). This is in ofcourse be in addition to having a way for > > > the user to indicate which files he is interested in and hence > > > those files should not be auto updated. Also maintaining a history > > > of updates in a separate directory would also help. This way in > > > case things do go wrong we still have access to the old files. > > > > > Could we not just check the last modified date vs. the create date > > and if they match, assume the file has not been altered? Or am I not > > as clear as I thought I was on what those two represent? > > Some people aren't eager to change a working configuration whether > they've made any changes or not. Okay. But might we consider an option in etc-update.conf or something like that so that those who don't mind it could try it? -- Ian Truelsen Email: [EMAIL PROTECTED] AIM: ihtruelsen Homepage: http://www.ihtruelsen.dyndns.org -- [EMAIL PROTECTED] mailing list
