Tres Melton posted <[EMAIL PROTECTED]>, excerpted below, on Thu, 14 Apr 2005 09:06:03 -0600:
> 1) I believe that 2004.3 is 'deprecated' (not depreciated) since the > other day when I did an esync it told me so. Thx for the spelling correction. With a bit of prompting, I remember the difference, but to reinforce it, I kdicted it, and found the following in the Jargon File reference: [Usage note: don't confuse this word with `depreciate', or the verb form `deprecate' with `depreciated`. They are different words; see any dictionary for discussion.] To the intended subject, however, are you /sure/ it was $PORTDIR/profiles/default-linux/amd64/2004.3 that was "deprecated"? Take a look at $PORTDIR/profiles/default-amd64-2004.2 for a deprecated profile. Note that the profile includes a "deprecated" file, which lists the recommended upgrade profile, what to do to upgrade, and includes the warning. Also note that said recommended upgrade profile is cascading 2004.3 profile as listed above, so why would they be deprecating that so quickly as well, particularly without even changing the pointers to it in the previously deprecated profiles? 2004.2, I knew was deprecated, in part because they are working to eliminate the non-cascading profiles. However, neither 2004.3 nor its lib64 subprofile have the deprecated file tagging them, here, at least after yesterday's sync (doing 2day's now). Further, there's been no discussion of such deprecation on either this list or the dev list, as there usually is, previous to it actually happening. Also... note that even the 2004.2 profiles deprecated file says people have until July 1, so it's not immediately urgent, tho urgency is rising... > 2) I also did the manual upgrade and for a while I had quite a few > pieces to keep. ;-) Because of that I disagree with your reasoning of > "the ability to give up and try again later, if desired." That's an unfortunate possibility. =8^( However, my reply was in the context of someone asking if he should give up, which implies his system isn't /that/ broken currently, or he'd not be asking. If the option continues to exist, I was simply saying there was no further issue in delaying until later -- until that deprecated warning appears. UPDATE: sync finished. Still no "deprecated" file in 2004.3. If you didn't get mixed up with a different profile, perhaps your sync server did, or perhaps someone made a mistake, and you happened to sync b4 it was corrected. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
