forums.ps2dev.org

(This has been split from the original post. - ooPo)

Uh - you should be checking out the trunk, not the tags. In linux, you do in a terminal
I have no troubles with anything doing a checkout that way.

J.F. wrote:Uh - you should be checking out the trunk, not the tags. In linux, you do in a terminal

Code: Select all

svn checkout svn://svn.ps2dev.org/ps2/trunk
svn checkout svn://svn.ps2dev.org/ps2ware/trunk

I have no troubles with anything doing a checkout that way.

I already said that there is no problem with 'checkout', as far as getting hold of the source code.
Why do you even bother to repeat this again ?

You clearly haven't understood the problem, so here is a brief clarification:

When you request a checkout or update for something in the 'trunk' that is not all you get. For technical reasons such operations implicitly require that corresponding sections of 'tags' and 'branches' are also transferred. Below I will refer to these just as 'tags', to keep things simpler...

In order to participate in development (the main purpose of SVN) it is not enough to just 'checkout' or 'update'. You must also be able to perform other more complex operations on the repository, and for that the system relies on information in 'tags' to resolve conflicts. And that is the reason why 'tags' stuff is always transferred, even if you only request stuff in 'trunk'.

Now, with the conflict of folder names that I mentioned earlier (start\ and START\ can't both exist in the same place under Windows), it becomes impossible for a Windows user to get some 'tags' information for the ps2ftpd project, and because of that he can't participate in that project.

This problem still needs to be fixed !!!

Best regards: dlanor

Judging by the lack of response or even notice of the problem, one could deduce that it isn't actually something that 'needs' to be fixed. Certainly not urgently, at least.

Restating it in a stern tone hasn't worked, nor has being short with someone who did take the time to respond in good faith in an attempt to help you.

I would suggest either moving to a development platform that doesn't require others to fix their contributions for you to join in, or fix it yourself.

ooPo wrote:Judging by the lack of response or even notice of the problem, one could deduce that it isn't actually something that 'needs' to be fixed. Certainly not urgently, at least.

I fail to understand your reasoning here. You seem to be saying that any problem of which the majority is unaware is inherently unimportant...

Restating it in a stern tone hasn't worked, nor has being short with someone who did take the time to respond in good faith in an attempt to help you.

A person who replies simply by rephrasing something I said in my second post (that checkout does deliver the sources) has not made any real effort to help. He was either being sarcastic or genuinely confused about what I meant, even though I had explained it twice already. So I took the time to explain it yet again (thus giving him the benefit of doubt). The only thing 'short' or 'stern' about my reply is that I questioned why he restated something I had said myself.

I would suggest either moving to a development platform that doesn't require others to fix their contributions for you to join in,

I never asked for any fix whatever specific to myself. What I asked for was a fix for something that currently blocks all users of Windows.

You may regard Windows as an odd and exotic platform if you wish, but the fact remains that it's what the majority of people are using. And if I am no longer welcome here for reporting compatibility problems with that 'strange' platform, then so be it.

or fix it yourself.

I'm sure you realize that I already would have done so, if I had such access. That kind of 'fix it yourself' comment is only appropriate when doing so is in fact possible, which is not at present the case here.

Best regards: dlanor

dlanor wrote:When you request a checkout or update for something in the 'trunk' that is not all you get. For technical reasons such operations implicitly require that corresponding sections of 'tags' and 'branches' are also transferred. Below I will refer to these just as 'tags', to keep things simpler...

In order to participate in development (the main purpose of SVN) it is not enough to just 'checkout' or 'update'. You must also be able to perform other more complex operations on the repository, and for that the system relies on information in 'tags' to resolve conflicts. And that is the reason why 'tags' stuff is always transferred, even if you only request stuff in 'trunk'.

Now, with the conflict of folder names that I mentioned earlier (start\ and START\ can't both exist in the same place under Windows), it becomes impossible for a Windows user to get some 'tags' information for the ps2ftpd project, and because of that he can't participate in that project.

Your svn software must be wacked. There are no start or START directories at all. SVN makes a .svn directory which hold the property directories, not a tags directory. There's no start/START directory there either. I would think the problem lies in the Windows software you are using to access the repository. I have a complete and working checkout of both the ps2 and ps2wares trunks, and don't see any of these directories you speak of. It seems to be a Windows problem. As such, you probably won't get much help here as most folks are using some posix based OS for PS2 dev.

Yo, J.F. -- you really ought to take the time to know what you are talking about before you make wild declarations that are wrong. dlanor has correctly described a problem with the svn archive on ps2dev. If you want to help you can do one of two things. Describe how tag names with the same name but different case are a problem. You should reference svn documentation.

If you aren't interested in learning how svn works and how to keep it operational, then at least prove your statement that most folks are using some posix based OS for PS2 dev. I use cygwin and linux. On cygwin the svn repository is broken just as dlanor says.

dlannor... what to do?

I fail to understand your reasoning here. You seem to be saying that any problem of which the majority is unaware is inherently unimportant...

If nobody is complaining, besides you, I can't see it being a major problem for people, besides you. Hence, inherently unimportant. Simple logic.

The only thing 'short' or 'stern' about my reply is that I questioned why he restated something I had said myself.

Its the only time that something is done that people remember. You've left an impression as being rude and without the basic knowledge to fix your own problems yourself.

I never asked for any fix whatever specific to myself. What I asked for was a fix for something that currently blocks all users of Windows.

Before responding, I waited for others to speak up with the same problem. This is how I judge the importance of a complaint or bug on a platform I do not personally use. If even one more person had spoken up I probably would have looked into it. Nobody did, so it was filed under a problem specific to yourself requiring a fix specific to yourself. Which is indeed what you're asking for.

You may regard Windows as an odd and exotic platform if you wish, but the fact remains that it's what the majority of people are using. And if I am no longer welcome here for reporting compatibility problems with that 'strange' platform, then so be it.

Get off the damn soapbox, princess. I never said odd NOR exotic, and I said nothing against Windows itself. I do think its a bad, bad, BAD thing to be using Cygwin to fake yourself into a proper unix environment but work has been done to specific support that very platform by myself and many others here - including those who have no intention of ever using it. While I may argue that it isn't what the majority of contributing people use, we all agree that it is important to support. Stop playing the drunken martyr and return to earth, spaceman.

...and look into running a proper, case-sensitive filesystem. That's what originally I meant, sunshine.

I'm sure you realize that I already would have done so, if I had such access. That kind of 'fix it yourself' comment is only appropriate when doing so is in fact possible, which is not at present the case here.

Even without access, Oobles has stated that he doesn't know how to fix it but he is welcome to you telling him how. A simple 'here is what is wrong and here is how it can be fixed, please' would have saved you a whole bunch of thumb twiddling and general ire.

(I'm splitting this thread to remove the drama.)