jmsellens@watdragon.waterloo.edu (08/25/89)
From: "John M. Sellens" <jmsellens> Since the mfcf "package" is doomed, and we are trying to move stuff out of it, but there are still things that refer to it in its /usr/mfcf/ incarnation, we end up with lots of duplicates and xhier complaints. Shoud xh-make-links treat the mfcf "package" specially and ignore conflicts with it and another package, and just make the link to the other correct package instead?? e.g. see this from grand (trimmed down a lot) | xh-make-links: conflicts between packages occured, no new links made | xh-make-links: conflicts are as follows: | mfcf/bin/ci | rcs/bin/ci | accounts/maintenance/add_all | mfcf/maintenance/add_all | accounts/servers/findall | mfcf/servers/findall | font/servers/fontd | mfcf/servers/fontd | mfcf/servers/texfontd | tex/servers/texfontd Software maintenance FROM HELL!!!!!!!!!!!! :-)
rbutterworth@watmath.waterloo.edu (Ray Butterworth) (08/25/89)
In article <16116@watdragon.waterloo.edu>, jmsellens@watdragon.waterloo.edu writes: > Since the mfcf "package" is doomed, and we are trying to move stuff out > of it, but there are still things that refer to it in its > /usr/mfcf/ incarnation, we end up with lots of duplicates and xhier > complaints. I think this is more or less what I'd been complaining about for a long time and finally gave up on. I guess it's your turn to carry the torch; you can have my proxy for deciding what to do with the mess. /usr/mfcf and /software/mfcf should never have been linked together. Old software could continue to use /usr/mfcf, and our new xhiered stuff could use /software/mfcf, and both would get along without any problem. Moving and linking the two made quite a mess of everything; it became impossible to rdist the mfcf package without breaking things since no two machines looked alike; and any attempt I made at correcting the situation made things worse. We made a similar mistake to the console package too I think. The only obvious solution that we could think of (other than putting things back the way they were before we messed them up) was to create other packages and move anything that seemed useful out of the mfcf non-package and into real packages that can be maintained and distributed. > Shoud xh-make-links treat the mfcf "package" specially and ignore > conflicts with it and another package, and just make the link to > the other correct package instead?? Sounds good to me. But there are only 8 programs left in the mfcf package on orchid. We should move them to a different package as soon as we can. That should fix things on all the properly xhiered machines. All the rest on watmath and other machines that were prematurely xhiered should be moved back to /usr/mfcf or where ever it was they were moved from. > Software maintenance FROM HELL!!!!!!!!!!!! :-) Send it back.