This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Retire the MPW support from toplevel and binutils



On Mar 25, 2004, at 7:31 AM, Andrew Cagney wrote:


I'm sure you already knew this, but you'll need to update the cvs modules for the repository at the same time you're doing this - these files are explicitly named in there:

Er, the modules file should _not_ be updated. You can always add, but never remove entries.

In this case, these support files have been obsolete for longer than the sourceware repositories have been live. From a completely maniacal outlook we'd never want to remove files like this, but looking at it realistically, there's nothing being lost here. Yes, if someone checks out binutils 2.10 (one of the first releases after the repositories moved to sourceware, circa June 2000) by a cvs command they'll be missing the mpw support files from the top level.


If the modules file is not updated, every checkout until the end of time will include

cvs checkout: warning: src/mpw-build.in is not (any longer) pertinent
cvs checkout: warning: src/mpw-README is not (any longer) pertinent
cvs checkout: warning: src/mpw-config.in is not (any longer) pertinent
cvs checkout: warning: src/mpw-configure is not (any longer) pertinent
cvs checkout: warning: src/mpw-install is not (any longer) pertinent


Which do you think is going to cause more questions and confusion: People checking out binutils 2.10 from CVS and being shocked that the mpw support files, which no longer do anything useful, are not present, or people checking out TOT and wondering what the heck these five missing files are and why they're not pertinent.


The modules file must be updated.

J


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]