Thomas Kuehne wrote:
<snip>
> Are you behind some HTTP proxy?

Yes.

> What happens if you try
> "svn co svn://dstress.kuehne.cn" instead of "svn co http://dstress.kuehne.cn"?
<snip>

That works!  But now the backup repository isn't letting me update:

[masg2-mac:d/dstress/dstress] masg2% svn update
subversion/svnserve/serve.c:1642: (apr_err=170001)
svn: No access allowed to this repository


And it still isn't helping me with getting into Dsource:

[masg2-mac:~/Downloads/d/dsource] masg2% svn co http://svn.dsource.org/projects/bindings
subversion/libsvn_ra_dav/util.c:670: (apr_err=175002)
svn: REPORT request failed on '/projects/bindings/!svn/vcc/default'
subversion/libsvn_ra_dav/util.c:294: (apr_err=175002)
svn: REPORT of '/projects/bindings/!svn/vcc/default': 400 Bad Request (http://svn.dsource.org)

[masg2-mac:~/Downloads/d/dsource] masg2% svn co svn://svn.dsource.org/projects/bindings
subversion/libsvn_ra_svn/client.c:151: (apr_err=60)
svn: Can't connect to host 'svn.dsource.org': Operation timed out


FTR here's the content of my .subversion/servers file:

[global]
http-proxy-host = wwwcache.lboro.ac.uk
http-proxy-port = 3128

Stewart.

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/M d- s:-@ C++@ a->--- UB@ P+ L E@ W++@ N+++ o K-@ w++@ O? M V? PS- PE- Y? PGP- t- 5? X? R b DI? D G e++>++++ h-- r-- !y
------END GEEK CODE BLOCK------

My e-mail is valid but not my primary mailbox.  Please keep replies on the 'group where everyone may benefit.

J C Calvarese wrote:
> In article <e0n1kg$14b8$1@digitaldaemon.com>, Stewart Gordon says...
<snip>
>> - arcane, undocumented features, e.g.  version (STANDALONE) in Core32
> 
> There's a simple purpose for version(STANDALONE), but it might be controversial.

The real problem is that nobody seems to know what that simple purpose is.

<snip>
> Since SVN is a problem on your Mac, maybe you could start a project at dsource
> and just use the Trac wiki to attach files. It's not ideal, but it's better than
> these newsgroups (IMO). There has to be something better than attaching the
> files to these newsgroups. The files can be decoded from the web interface, but
> it sure slows a person down when they don't have a news reader available.
<snip>

You mean I should set up some pages on the wiki on which to post files?  Hmm....

Stewart.

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/M d- s:-@ C++@ a->--- UB@ P+ L E@ W++@ N+++ o K-@ w++@ O? M V? PS- PE- Y? PGP- t- 5? X? R b DI? D G e++>++++ h-- r-- !y
------END GEEK CODE BLOCK------

My e-mail is valid but not my primary mailbox.  Please keep replies on the 'group where everyone may benefit.

In article <e0rfim$145j$1@digitaldaemon.com>, Stewart Gordon says...
>
>J C Calvarese wrote:
>> In article <e0n1kg$14b8$1@digitaldaemon.com>, Stewart Gordon says...
><snip>
>>> - arcane, undocumented features, e.g.  version (STANDALONE) in Core32
>> 
>> There's a simple purpose for version(STANDALONE), but it might be controversial.
>
>The real problem is that nobody seems to know what that simple purpose is.

Firstly, I thought I answered your question about this back in 2005.

Your question: http://www.digitalmars.com/drn-bin/wwwnews?digitalmars.D/15262

Perhaps you missed my reply: http://www.digitalmars.com/drn-bin/wwwnews?digitalmars.D/15265

The whole thread for context: http://www.digitalmars.com/d/archives/digitalmars/D/15248.html


But I'll try to do a better job of explaining...


*What does version(STANDALONE) do?*

Core32 is meant to complement Phobos.

If someone doesn't want to import std.c.windows.windows, they would compile with the version=STANDALONE set.

The default (compiling without the STANDALONE version set) has many of the conflicts with Phobos versioned out.

We've tried to add "version(STANDALONE)" to all of  the statements that are also in Phobos. DMD doesn't complain about conflicts until they are actually mentioned in code that uses both. Some of the conflicts were found by tediously comparing std.c.windows to the Core32 files, and other conflicts were found by "blah conflicts with blah" error statements from DMD. I guess if I were smart I'd come up with some sort of automated tool to find all of the conflicts once and for all, but for now I just version out the conflicts when I become aware of them.


*What is the future of Core32?*

(No one else has asked me this question, but I've been asking it to myself.)

It's pretty bleak. The guy who originally ported the Windows API headers disappeared quite a while ago.

I'd been updating the files some, but I've lost interest in updating Core32, too. Everyone else just wants to complain about it. I haven't even been using it. I don't think anyone really wants to use Core32. Its freckles turned out to be carcinoma. I've thought about fixing some of the problems that have been accumulating, but I don't really see the point anymore.

Your new Windows API project seems to be gaining momentum. If it continues to be productive, I don't have an interest in competing. I'd rather occasionally help out with the new team than continue to spend time with Core32.


><snip>
>> Since SVN is a problem on your Mac, maybe you could start a project at dsource and just use the Trac wiki to attach files. It's not ideal, but it's better than these newsgroups (IMO). There has to be something better than attaching the files to these newsgroups. The files can be decoded from the web interface, but it sure slows a person down when they don't have a news reader available.
><snip>
>
>You mean I should set up some pages on the wiki on which to post files?
>  Hmm....
>
>Stewart.

Actually, what Don is doing in the Bindings project is probably the best solution until you get your SVN problem solved (assuming there is a fix).

jcc7

jcc7 wrote:
> In article <e0rfim$145j$1@digitaldaemon.com>, Stewart Gordon says...
>> J C Calvarese wrote:
>>> In article <e0n1kg$14b8$1@digitaldaemon.com>, Stewart Gordon says...
>> <snip>
>>>> - arcane, undocumented features, e.g.  version (STANDALONE) in Core32
>>> There's a simple purpose for version(STANDALONE), but it might be controversial.
>> The real problem is that nobody seems to know what that simple purpose is.
> 
> Firstly, I thought I answered your question about this back in 2005.
> 
> Your question: http://www.digitalmars.com/drn-bin/wwwnews?digitalmars.D/15262
<snip>

Sorry I'd half forgotten about that thread.  But it certainly ought to be in project documentation and not just one or two newsgroup posts.

> But I'll try to do a better job of explaining...
> 
> *What does version(STANDALONE) do?*
> 
> Core32 is meant to complement Phobos. 
> 
> If someone doesn't want to import std.c.windows.windows, they would compile with the version=STANDALONE set.
> 
> The default (compiling without the STANDALONE version set) has many of the
> conflicts with Phobos versioned out. 

I see.  So there's a difference in purpose between the two efforts. Mine is intended to be a full translation of the Windows API headers that might one day be able to replace std.c.windows.windows.

<snip>
> Your new Windows API project seems to be gaining momentum. If it continues to be productive, I don't have an interest in competing. I'd rather occasionally help out with the new team than continue to spend time with Core32.

OK.

<snip>
> Actually, what Don is doing in the Bindings project is probably the best solution until you get your SVN problem solved (assuming there is a fix).

I'm not sure what you mean.  By "what Don is doing" do you mean committing updates to that project on my behalf?

Stewart.

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/M d- s:-@ C++@ a->--- UB@ P+ L E@ W++@ N+++ o K-@ w++@ O? M V? PS- PE- Y? PGP- t- 5? X? R b DI? D G e++>++++ h-- r-- !y
------END GEEK CODE BLOCK------

My e-mail is valid but not my primary mailbox.  Please keep replies on the 'group where everyone may benefit.

In article <e0tm7q$mbn$1@digitaldaemon.com>, Stewart Gordon says...
>
>jcc7 wrote:
>> In article <e0rfim$145j$1@digitaldaemon.com>, Stewart Gordon says...
>>> J C Calvarese wrote:
>>>> In article <e0n1kg$14b8$1@digitaldaemon.com>, Stewart Gordon says...
>>> <snip>
>>>>> - arcane, undocumented features, e.g.  version (STANDALONE) in Core32
>>>> There's a simple purpose for version(STANDALONE), but it might be controversial.
>>> The real problem is that nobody seems to know what that simple purpose is.
>> 
>> Firstly, I thought I answered your question about this back in 2005.
>> 
>> Your question: http://www.digitalmars.com/drn-bin/wwwnews?digitalmars.D/15262
><snip>
>
>Sorry I'd half forgotten about that thread.  But it certainly ought to be in project documentation and not just one or two newsgroup posts.

You're right, and it is in the documentation now. I thought it was already there, but I was wrong.


>> But I'll try to do a better job of explaining...
>> 
>> *What does version(STANDALONE) do?*
>> 
>> Core32 is meant to complement Phobos.
>> 
>> If someone doesn't want to import std.c.windows.windows, they would compile with the version=STANDALONE set.
>> 
>> The default (compiling without the STANDALONE version set) has many of the conflicts with Phobos versioned out.
>
>I see.  So there's a difference in purpose between the two efforts. Mine is intended to be a full translation of the Windows API headers that might one day be able to replace std.c.windows.windows.

And hopefully we can get Walter to accept it when it's complete. And update it if someone finds a little room for improvement later.

<snip>

>> Actually, what Don is doing in the Bindings project is probably the best solution until you get your SVN problem solved (assuming there is a fix).
>
>I'm not sure what you mean.  By "what Don is doing" do you mean committing updates to that project on my behalf?

Yes, that's what I mean. Sorry if it sounded enigmatic.

jcc7

Stewart Gordon schrieb am 2006-04-03:
> Thomas Kuehne wrote:
><snip>
>> Are you behind some HTTP proxy?
>
> Yes.
>
>> What happens if you try
>> "svn co svn://dstress.kuehne.cn" instead of
>> "svn co http://dstress.kuehne.cn"?
><snip>
>
> That works!

Looks like your HTTP proxy doesn't support/allow:
REPORT, MERGE, PROPFIND, LOCK, UNLOCK, DELETE, MKACTIVITY,
CHECKOUT, COPY, MKCOL, PUT, OPTIONS, PROPPATCH, CONNECT.

If the proxy is a forced one you are out of luck unless you can tunnel out (e.g. ssh) or get the proxy administrator to allow the listed methods.

Thomas

Thomas Kuehne wrote:
> Stewart Gordon schrieb am 2006-04-03:
> 
>>>Thomas Kuehne wrote:
>>><snip>
>>>
>>>>Are you behind some HTTP proxy?
>>>
>>>Yes.
>>>
>>>
>>>>What happens if you try
>>>>"svn co svn://dstress.kuehne.cn" instead of
>>>>"svn co http://dstress.kuehne.cn"?
>>>
>>><snip>
>>>
>>>That works!
> 
> 
> Looks like your HTTP proxy doesn't support/allow:
> REPORT, MERGE, PROPFIND, LOCK, UNLOCK, DELETE, MKACTIVITY,
> CHECKOUT, COPY, MKCOL, PUT, OPTIONS, PROPPATCH, CONNECT.
> 
> If the proxy is a forced one you are out of luck unless you can tunnel out (e.g. ssh) or get the proxy administrator to allow the listed methods.
> 
> Thomas
> 
> 

Thomas,

Did you have to do anything in the SVN or Apache configs to enable the svn:// protocol?  Did you have to open up a new port in your firewall?

BA

Brad Anderson schrieb am 2006-04-04:
> Did you have to do anything in the SVN or Apache configs to enable the svn:// protocol?  Did you have to open up a new port in your firewall?

http://svnbook.red-bean.com/en/1.1/ch06s03.html

Thomas

Thomas Kuehne wrote:
> Brad Anderson schrieb am 2006-04-04:
> 
>>>Did you have to do anything in the SVN or Apache configs to enable the svn:// protocol?  Did you have to open up a new port in your firewall?
> 
> 
> http://svnbook.red-bean.com/en/1.1/ch06s03.html
> 
> Thomas
> 
> 

I thought I'd try the easy way, but you rightfully slapped me back to the documentation.

BA

Stewart Gordon wrote:
<snip>
> The main open issue I can think of at the moment is what to do with the Windows version CC stuff.
<snip>

For those who haven't noticed already, I now have a proposal - mapping version identifiers to _WIN32_WINDOWS, _WIN32_WINNT and _WIN32_IE themselves.  See the wiki page for how this will work.  I've started implementing it and will probably upload it soon.

There are numerous other versioning #ifdefs in the C headers.  How many of them do we really need?  I'm in the process of rounding up a list of them....

And by the way, __USE_NTOSKRNL__ is apparently the NT OS kernel, not the N to S kernel.

Stewart.

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/M d- s:-@ C++@ a->--- UB@ P+ L E@ W++@ N+++ o K-@ w++@ O? M V? PS- PE- Y? PGP- t- 5? X? R b DI? D G e++++ h-- r-- !y
------END GEEK CODE BLOCK------

My e-mail is valid but not my primary mailbox.  Please keep replies on the 'group where everyone may benefit.