Re: [PyCS-devel] Helloooo!

[Phillip P. <ph...@my...>]

> Now, i should also mention that because i'm doing all this on windows, i
> could not run the makefile, so i've had to manually create all the
> directories and put all the file where they should go (reading a makefile
is
> a bit of a pain! ;). One thing that i noticed is that the weblogUpdate.py
> file is not in the /system directory in the .gz download file - i had to
> manually move the weblogUpdate.py file to the system dir. In the /system
dir
> is only 'update.py'... Not sure if that has anything to do with it, but
this
> always fails when it follows the 'recently updated' link which points to
the
> weblogUpdate.py script.

Aha - here's what you need to do:

- use the version from CVS rather than the .gz file, which is probably
horribly out of date.  As well as having loads of new features, it's
probably heaps more stable ;)

- there _is_ a weblogUpdates.py in the /system directory; it's just that
there's _another_ one in the root.  That's where they're meant to be: the
one in the root is the handler for the weblogUpdates XML-RPC call (that's
the one that puts you on the updates page), and the one in /system is the
updates page itself.

If you check out the archive and copy both of those into the right places,
then restart, you'll probably find that your weblog updates will work again.

Actually, now that I think about it, it used to work on Windows if you just
extracted everything into a directory and ran from there.  You certainly
don't need to copy everything into /var/lib/pycs and stuff.  Read
pycs_paths.py though - it should have some details about where things go on
Windows, which is a bit simpler than on Linux.  (This is one of the things
that is probably different in CVS and in the .gz on SourceForge).

Cheers,
Phil :)