> Seriouly... did you really belive I'd try my luck with something like > MVS ?
One never knows ;-) > > Just that "some kind of iffe-like probe" seems nebulous. How confident > > are we that we understand its purpose and relationship to Solaris? > > See Glenn's answer > (http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/2007-March/002429.html) > for that... He's described what it does, but said "I'm not sure how/where the catalog generation is being integrated" -- in other words, I still don't quite understand when we would make use of it. > > For hygiene reasons, we don't permit exceptions that are not actually > > being used. There is another tool (checkpaths) that will enforce this. > > (Yes, we're really *that* picky about this sort of stuff.) > > Ok... > ... but are there any objections that someone stuffs a DocBook/XML file > (documentation) in the tree (later... not now...) ? Seems OK to me, but that's something that probably needs discussion with a wider audience. > Well, my idea was to create a file (e.g. > "usr/src/lib/libshell/misc/filelist.txt") which should contain the list > of added/moved/removed files that we can keep track of all the movements > of our citizen. For now the file would only contain the following list > of removed files (plus CDDL header+description... and maybe a "removed" > in front of each filename): That seems OK to me. > usr/src/cmd/ast/msgcc/Mamfile > usr/src/lib/libast/common/Mamfile > usr/src/lib/libast/common/Makefile > usr/src/lib/libast/common/astsa/align.h > usr/src/lib/libast/common/astsa/astwinsize.c > usr/src/lib/libast/common/astsa/ccode.h > usr/src/lib/libast/common/astsa/strmatch.c > usr/src/lib/libast/common/astsa/times.h > usr/src/lib/libast/common/astsa/sig.h > usr/src/lib/libast/common/astsa/lclib.h > usr/src/lib/libast/common/astsa/README > usr/src/lib/libast/common/astsa/ast.h > usr/src/lib/libast/common/uwin/mini.sym > usr/src/lib/libast/common/misc/magic.tab > usr/src/lib/libcmd/common/Mamfile > usr/src/lib/libcmd/common/Makefile > usr/src/lib/libdll/common/Mamfile > usr/src/lib/libdll/common/Makefile > usr/src/lib/libpp/common/Mamfile > usr/src/lib/libpp/common/Makefile > usr/src/lib/libpp/common/probe.win32 > usr/src/lib/libshell/common/Mamfile > usr/src/lib/libshell/common/Makefile > usr/src/lib/libshell/common/mamexec > usr/src/lib/libshell/common/mamstate.c > -- snip -- > (please verify that I didn't miss any files) I thought we concluded that dirstd.h and atmain.C were also safe to remove? > > > > ./lib/libpp/sparc/probe > > > > ./lib/libpp/sparc/probe.sh > > Uhm... good question. Glenn explained in > http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/2007-March/002429.html > for which stuff these files are used... but the OS/Net Makefiles do not > use them (which raises the question why these files didn't show up in > the original "unused i386 files"-list). Indeed, why is that? -- meem
