Ben Bangert wrote:
On Nov 16, 2005, at 2:34 PM, Ian Bicking wrote:
I would also think that if the source view is going to be separate
files under a dir, the directory should be an option in setup.cfg, like
source_dir = source
That could be a pudge option. But it isn't right now. I don't see
any particular motivation to create it, though.
On my site, I stuck my svn directory under routes.groovie.org/routes
rather than routes.groovie.org/svn. So now I have to change my Apache
config to accommodate Pudge. I could see many reasons why people would
want some control over where the source hilighted files go.
Hmm... I guess I see the issue. I suppose, even if the package names
are kept in the paths, you could give a base directory (default '').
But like I said, it doesn't really effect me; I'm sure Ryan will give
you commit access if you want to make the change.
Anyway, buildutils is fixed, so the publish command should preserve
directories. I broke it when I added filtering to publish.
I tried the latest version, it did create the sub-dirs. However it
didn't upload any of the hi-lighted files, it did upload a file I
manually specified in a docs sub-dir. However, now none of the files in
just docs/html are being uploaded at all so its even more broke than
before.
Did you try --force? I'm afraid my _last_upload_signatures.txt
"optimization" is not very clever, and can't tell that you'll now be
uploading files to a new location (since the previous upload worked, but
was buggy in a different way that the signatures couldn't know about).
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
_______________________________________________
Pudge mailing list
[email protected]
http://lesscode.org/mailman/listinfo/pudge
