Fresh SVN-install yields "link stdnormal_footer" on all subpages
Hi,
I just did a fresh SVN install of 4.3b3 (4.3.0-0.20101114.beta3) and on all my subpages I get the "link stdnormal_footer" written in plain-text. Seems like all the footer-files in the webfiles/web-directory contains that string - shouldn't they simply symlink to the stdnormal_footer file?
Regards,
Carl Melgaard
In <3BD667CCFBD0D04CA2BC3D57D01B64264CA04A5C62 at HORMXB103VM1.onerm.dk> Carl Melgaard <Carl.Melgaard at STAB.RM.DK> writes:
I just did a fresh SVN install of 4.3b3 (4.3.0-0.20101114.beta3) and on all= my subpages I get the "link stdnormal_footer" written in plain-text. Seems= like all the footer-files in the webfiles/web-directory contains that stri= ng - shouldn't they simply symlink to the stdnormal_footer file?
How did you download the sourcecode - just the file available from the "Files" section of Sourceforge, or as a checkout from SVN ? If the latter, did you use a Unix-version of the SVN utilities ?
Downloading using a Windows-based SVN client is unlikely to work, since Windows doesn't support symbolic links.
Regards, Henrik
ng - shouldn't they simply symlink to the stdnormal_footer file? How did you download the sourcecode - just the file available from the "Files" section of Sourceforge, or as a checkout from SVN ? If the latter, did you use a Unix-version of the SVN utilities ?
Downloading using a Windows-based SVN client is unlikely to work, since Windows doesn't support symbolic links.
Actually, I just did a web-download "GNU-tarball" from the branches/4.3.0/ directory. Guess that doesn't work either. I'll just fix the symlinks manually - is there anything else that might be broken this way?
Regards,
Carl Melgaard
ng - shouldn't they simply symlink to the stdnormal_footer file? How did you download the sourcecode - just the file available from the "Files" section of Sourceforge, or as a checkout from SVN ? If the latter, did you use a Unix-version of the SVN utilities ?
Downloading using a Windows-based SVN client is unlikely to work, since Windows doesn't support symbolic links.
Actually, I just did a web-download "GNU-tarball" from the branches/4.3.0/ directory. Guess that doesn't work either. I'll just fix the symlinks manually - is there anything else that might be broken this way?
That's right - the tarball from the web svn breaks the symlinks - fortunately these are the only files affected.
Henrik, couldn't we dispense with putting symlinks into SVN and generate them during the build instead?
Malcolm
-- Wouldn't the sentence "I want to put a hyphen between the words FISH and AND and AND and CHIPS in my FISH-AND-CHIPS sign" have been clearer if quotation marks had been placed before "FISH," and between "FISH" and "and," and "and" and "AND," and "AND" and "and," and "and" and "AND," and "AND" and "and," and "and" and "CHIPS," as well as after "CHIPS?"
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
In <20101209132829.219710 at gmx.net> "Malcolm Hunter" <malcolm.hunter at gmx.co.uk> writes:
ng - shouldn't they simply symlink to the stdnormal_footer file? How did you download the sourcecode - just the file available from the "Files" section of Sourceforge, or as a checkout from SVN ? If the latter, did you use a Unix-version of the SVN utilities ?
Downloading using a Windows-based SVN client is unlikely to work, since Windows doesn't support symbolic links.
Actually, I just did a web-download "GNU-tarball" from the branches/4.3.0/ directory. Guess that doesn't work either. I'll just fix the symlinks manually - is there anything else that might be broken this way?
That's right - the tarball from the web svn breaks the symlinks
Really ?!!? <checking> WTF .... You're right. Sourceforge bug, in my book.
Henrik, couldn't we dispense with putting symlinks into SVN and generate them during the build instead?
It's just much simpler to have them in the source-tree. And "svn co" works fine, as does the "svn export"-generated files.
I'll think about it.
Regards, Henrik
participants (3)
-
Carl.Melgaard＠STAB.RM.DK
-
henrik＠hswn.dk
-
malcolm.hunter＠gmx.co.uk