Open GoogleCodeExporter opened 8 years ago
Just change /svn/trunk/.svn/dir-prop-base so it reads
V 58
PyFR http://frontpython.googlecode.com/svn/trunk/SDK/PyFR
rather than
V 59
PyFR https://frontpython.googlecode.com/svn/trunk/SDK/PyFR
Fixed here [locally], but to do so, you must use 'svn checkout
--ignore-externals http://pyetv.googlecode.com/svn/trunk pyetv', edit the file,
then .svn up'. This should be fixed on the server.
Original comment by d235...@gmail.com
on 22 Mar 2009 at 6:28
I personally have write access to the frontpython repo, and so my dev
environment
has PyFR checked out via https so that I can commit changes.
Of course that breaks it for the rest of the world. Great.
If anyone has a better svn-foo than I do and can tell me how to set
this up so that I:
1) don't have to maintain a separate tree
2) can commit to both PyeTV and PyFR from the same source tree.
3) can set up the PyeTV dependency on PyFR in svn.
I'd appreciate it.
Original comment by jon.chri...@gmail.com
on 26 Mar 2009 at 1:20
Why make it so complicated??? It doesn't seem so smart.
I just want to download some files, but now I have already wasted hours on
trying to
download, install and run some kind of rediculous SVN client. Who is
responsible for
all this? Probably some "smart" Linux hacker who hates userfriendly software.
Einstein said: Keep it simple!
Original comment by nilsthor...@gmail.com
on 31 Mar 2009 at 5:30
nilsthorell,
I think you meant to say "Thank you for using your limited free time to provide
me
useful software free of cost".
If you want simple, download the binary which I, personally, have no use for,
but go
out of my way to provide as a public service.
If you want to hack on the source, then I'm afraid you'll have to learn the
development tools, which google has selected and hosted as a public service.
And finally, for your information, there are many user friendly svn clients out
there. A google search for "mac svn" turns up many.
Original comment by jon.chri...@gmail.com
on 1 Apr 2009 at 4:56
If you modify the svn to use http, perhaps you could check out PyFR seperately
and symlink the required
directory into your build tree, in place of the one you checked out as the
external for PyeTV. Then it would check
out right for others.
Just a thought. Thanks for doing this.
Bill
Original comment by w.northc...@unsw.edu.au
on 27 Dec 2009 at 2:20
Original issue reported on code.google.com by
shin...@gmail.com
on 27 Dec 2008 at 11:21