Re: [VK] Newsletter #1

[Paul E. <pe...@ca...>]

Hi again!

Hope you really wanted feedback, seeing as this is my second post today :-)

>          For if you don't want to use CVS, or if don't have it installed on
>          your system, you may also download the daily tar-ball, generated
>          from the CVS:
> http://cvs.sourceforge.net/cvstarballs/viskprog-cvsroot.tar.gz

I copied and pasted the above link and:
I don't know what you think is in the tarball, but it's not there!


Having no clue about cvs other than a vague notion of rcs, I grabbed the
above tarball. Also, I should point out that the newsletter said that 
>          For if you don't want to use CVS, or if don't have it installed on
>          your system, you may also download the daily tar-ball, generated
>          from the CVS:

I know I said that allready, but I'm just pointing it out. The clown show below
is the result of being told I didn't need to have CVS installed on my system
to use the tarball. Please don't say that anymore :-)


Everything inside is appended with ',v' like cvs, so..... I took them off !!
This took quite a while....
That was stupid, there's cvs stuff inside each file. Who knew? So, that was a
waste of time, of course. Deleted and started again.

Typed cvs at a prompt, but this did not help, but hey! remembered cervisia,
tried that.

Went and set up a CVSROOT envar, logged out and back in again.

Tried cervisia some more.

Read the other help in the menu and gave cvs init a shot. This worked.
Tried cervisia some more. Managed to begin importing my entire home dir.
Those labels really aren't that clear to newbies. Aborted this good sport.

Tried again with the dirs from the tarball. Success!!

Went and read the cvs docs some more. Tried to checkout visk module and it
worked! Now I find all the files are still cvs. Look into my CVSROOT and see
they are all ,v,v. Sigh. Delete everything and start again.

Just copy the dirs from the undone tarball into my CVSROOT and type
cvs checkout dirnames  and NOW it works. :-) I am now all happy!

Now I compile and install the base. Things go well, but I notice suspicious
1.8's here and there.

Now I go into the ide. No configure. I read through the files. I read in the 
configure.in file that I should use autoconf. Used that, but it gave it
as standard out. Confused (again). Read the --help for autoconf and found it
hates args. OK. run again without args. Makes a configure!

Happy again. So, ./configure. chunka chunka chunka.
Type make and : -> no targets.
sed was looking for a Makefile.in, but I didn't have one. Cloned the
Makefile.am into Makefile.in in the hope that it might help.

Did it again. No errors, but Same results. I have now given up on it again for a
while.

All the datestamps are in the file are still May. Just like it says at source
forge everything's older than 3 months.

I'm writing you all this, just so that you know how helpless some of your
audience really is. Maybe it's of some use to you when writing visk. Maybe good
for a laugh anyway. I still really want to try viskprog out.

Now, I wonder where the tarball I was after from the newsletter is?

One good thing: now that I've set up cvs I can try that in different places in
the future.

Regards, Paul

--== Paul Evans ==--
 pe...@ca...