On Sun, 20 Aug 2000, Mallard pushed some tiny letters in this order:
> Thanks for wasting the two hours I had today to do some programming!
>
Ahh, now I'm beginning to understand. You must have a grudge against Linux that
helps to justify any money spent on buying MS Windows. You might have some
valid complaints about vi before. It isn't that easy to use if you've never
seen it before and perhaps it shouldn't be the default to help the new users.
But you're not going to get on anyone's good side by posting a page long rant
to a mailing list when you've had a bad day. Please go back to Windows or go
back under your bridge troll.
http://everything.blockstackers.com/everything.pl?node=troll
> I was compiling just fine in 7.0 after figuring out how to install
> everything I needed. now I do a clean install of 7.1 "developer" and
libstdc++ DOES install as part of developer unless you change the
packages or otherwise play with the package percentage slider. It has been
remarked in the past that the slider is a bit confusing and perhaps Mandrake
has taken that on board. If you're SO annoyed with rpmDrake then don't use it!
Use kpackage which is preinstalled, or maybe Glint from redhat's distribution
will suit you better.
>
> Then I do another lame thing, go into file manager root>mnt>cdrom so I
> can see my cdrom (no mandrake couldn't have made little easy to find
> links for them, too busy playing doom or something to spend 2 minutes
> making things easier for the 1000's of users that will get your dist) -
What?? Off the top of my head I can remember plenty of ways to get to the CD
ROM; The desktop icon in KDE, the desktop icon in GNOME, KDE's disk navigator,
any one of the many file managers, not to mention a console. If you can
suggest a faster way than all of these to access a cdrom then figure out how to
do it, and enlighten us with how you did it. The program you are talking
about (kfm) is actually developed by the KDE team and Mandrake aren't
responsible if it doesn't have cutesy [D:] icons on the main tree for you. So
don't get all whiney at Mandrake if you're too lazy to click a few times.
> then I find the file is on the main CD, but no it's not the file, it's
> some other c++ goodie I have no clue what is for, so I don't think it's
> here at all. WHY NOT? Is there a more $$ version with this ONE FILE in
> it?
>
> OK, so I go to the main site and do a search, try it, try to find it.
> What the hell was it called? I don't remember, should have writen it
> down. But geeks always write this stuff down, that's the point, we want
> you to not have a life like we do, suffer like us, that's what Linux is
> all about, "I wasted my life figuring this out, so I will now make
> others do it too!" - is that the motto here?
If you need to remember something complex it's always pays to write it down.
Again, don't blame Mandrake if you have a failing memory.
>
> So I decide to get smart ass, I am gonna get it from 7.0 and screw you
> too! So I find it on 7.0, no thanks to the BROKEN search feature in
> drakeRPM, looking for fstream.h, and the way you have to tell it to go
> look on the cdrom, what type of user interface is that called?
>
> I find it and try to use kpackage to install it. It does, but in
> usr/include/c++-2/ that's the secret directory. So now it should make
> just fine, RIGHT?
>
> No, because make or gcc or whatever is configured to look in another
> newer directory that mandrake made up FOR SOME REASON (HINT HINT???)
> called c++-3 even though it's the same files. So like the smart ass I am
> I make a directory called that and put the files in there.
>
> AH HA! make finds the files and compiles, but wait! MORE ERRORS? on a
> program that compiled just fine before? YES!! ios() has errors! it
> didn't before, so now what???
>
You can't reasonably expect that grabbing old files and replacing the latest
ones with them to go off without a hitch? Did you consider that the directories
were different because newer versions of the old files were incompatible with
a newer compiler version??
Tony
