On Monday, 8 July 2013 at 19:37:08 UTC, JohnnyK wrote:
Another thing about GitHub's Download Zip button and this process as a whole.  While the Download Zip button does allow you to download the master folders with recursive directories I do find it somewhat cumbersome or should I say awkward since you have to extract these in their correct locations upon download.  This is not good when you are trying to follow someones instructions on how to download, build, and install their wares.  I just don't get git?  Just compile the code and put a binary up there for people to use.  If I want to contribute to the code base then I will I guess go through all this hassle but for those of us not smart enough to contribute and just want to use it show me the binary please.  In the amount of time it is taking to get this stuff I could have made major strides at building my own.  Also I don't know what this fragmented downloading is going to do in the future when I want an updated version of the software.  Please remember many of us are simpletons and don't use all these fancy version control systems and just need the binary so that we can use it.  I guess you could say we are your customers and not your contributors.  Please everyone in the D community try and follow the KISS methodology and if you do I bet you could get many more users of your wares and not people banging their heads until they give up.  Yeah I was only 2 clicks away from giving up on this whole D thing thinking it was just too darned hard to make it worth my while.  Who knows I still may give up since I have not attempted to compile it yet.  I think I will wait until tomorrow before I try to tackle that part of the destruction's.  For now I think I have it downloaded.  BTW did I mention that I really hate git and compiling other people's code just to use an edit box and button on a dialog???

On Monday, 8 July 2013 at 19:57:52 UTC, JohnnyK wrote:
> On Monday, 8 July 2013 at 19:37:08 UTC, JohnnyK wrote:
> Another thing about GitHub's Download Zip button and this process as a whole.  While the Download Zip button does allow you to download the master folders with recursive directories I do find it somewhat cumbersome or should I say awkward since you have to extract these in their correct locations upon download.  This is not good when you are trying to follow someones instructions on how to download, build, and install their wares.  I just don't get git?  Just compile the code and put a binary up there for people to use.  If I want to contribute to the code base then I will I guess go through all this hassle but for those of us not smart enough to contribute and just want to use it show me the binary please.  In the amount of time it is taking to get this stuff I could have made major strides at building my own.  Also I don't know what this fragmented downloading is going to do in the future when I want an updated version of the software.  Please remember many of us are simpletons and don't use all these fancy version control systems and just need the binary so that we can use it.  I guess you could say we are your customers and not your contributors.  Please everyone in the D community try and follow the KISS methodology and if you do I bet you could get many more users of your wares and not people banging their heads until they give up.  Yeah I was only 2 clicks away from giving up on this whole D thing thinking it was just too darned hard to make it worth my while.  Who knows I still may give up since I have not attempted to compile it yet.  I think I will wait until tomorrow before I try to tackle that part of the destruction's.  For now I think I have it downloaded.  BTW did I mention that I really hate git and compiling other people's code just to use an edit box and button on a dialog???

Ar you talking about D specifically? You *can* just download the package you know:
http://dlang.org/download.html
I'm actually wondering how you even reached git?

On Monday, 8 July 2013 at 19:20:46 UTC, John Colvin wrote:
> I don't see how it is problematic? The firewall doesn't allow a particular type of connection, so you cache the result somewhere else and then access it via something that is allowed.
>
> It's the same as downloading the zip file from github, only you're doing the "zipping" yourself, then using scp to do the download instead of http.
>
> Is it common to have ssh connections banned in the IT policy but *not* blocked by the firewall?

I'm just saying that maybe the firwall is blocking that protocol on purpose? Github can very easily be seen as "File Sharing" and/or "Online Storage". The sole act of downloading/uploading anything on there is possible violations of policy. You could download viruses, or be stealing your company's code to publish it online. Even if you *can* download the zip via http, it doesn't mean you are actually allowed to. If your company's firewall doesn't block a porn site, does that means its OK to surf it?

Now, most companies wouldn't really care that much about it, if you connect every now and then, no one will care. Worst case scenario, you'll get a reminder not to download/upload crap on internet.

But, if you start doing all this via ssh, or other alternative routes, then you are *activelly* bypassing protections, and in particular, doing something you *know* you shouldn't be doing. That's a more serious offense.

Now, do what you want. I'm just saying before going it and deploying such tools to download the files on git, please make sure you aren't violating your company's policies.

On Tuesday, 9 July 2013 at 08:55:29 UTC, monarch_dodra wrote:
> On Monday, 8 July 2013 at 19:20:46 UTC, John Colvin wrote:
>> I don't see how it is problematic? The firewall doesn't allow a particular type of connection, so you cache the result somewhere else and then access it via something that is allowed.
>>
>> It's the same as downloading the zip file from github, only you're doing the "zipping" yourself, then using scp to do the download instead of http.
>>
>> Is it common to have ssh connections banned in the IT policy but *not* blocked by the firewall?
>
> I'm just saying that maybe the firwall is blocking that protocol on purpose? Github can very easily be seen as "File Sharing" and/or "Online Storage". The sole act of downloading/uploading anything on there is possible violations of policy. You could download viruses, or be stealing your company's code to publish it online. Even if you *can* download the zip via http, it doesn't mean you are actually allowed to. If your company's firewall doesn't block a porn site, does that means its OK to surf it?
>
> Now, most companies wouldn't really care that much about it, if you connect every now and then, no one will care. Worst case scenario, you'll get a reminder not to download/upload crap on internet.
>
> But, if you start doing all this via ssh, or other alternative routes, then you are *activelly* bypassing protections, and in particular, doing something you *know* you shouldn't be doing. That's a more serious offense.
>
> Now, do what you want. I'm just saying before going it and deploying such tools to download the files on git, please make sure you aren't violating your company's policies.

  I do not encourage anyone to bypass network security protections and I do encourage letting your conscious be your guide on this topic.

  The issue is that it is just more complicating than I think it should be to download libraries and such.  Authors of helper libraries and other D related code should take their queue from dlang.org and actually have binaries that users can download and just use without the need to compile before they can use the wares.  It is not a firewall issue or anything like that.  It was just GIT not supporting modern proxy authorization schemes.  Problem resolved but it could have been avoided all together for those of us that are not to the point of contributing to these projects and are just trying to get their feet wet without drowning first.
On another note I was able to successfully compile the DWT lib and I was able to compile the snippet example programs to test DWT.  I did notice for those that are interested DWT exe's are over 2MB which is really what I was wanted to find out.  I will redirect DWT questions to the appropriate forum.

  The workaround for GIT via proxy is just not as pretty as I would have liked it.  However as I posted previously I found a suitable workaround for the issue.  No other discussion is needed for this issue.