On 5/25/13 3:14 PM, Nick Sabalausky wrote:
> On Sat, 25 May 2013 11:41:17 -0700
> Walter Bright<walter@digitalmars.com>  wrote:
>>
>> Unfortunately, zip on linux does not run on windows, and windows
>> doesn't have an ssh host.
>>
>
> Genuine question, not sarcasm: What would the Windows-hosted ssh be
> needed for? Maybe there's another way to achieve the same effect, like
> running an SFTP server on the linux side?

I'd love ssh access to a Windows host. The best scenarion for building the installer is to start from a Unix machine (which has all those command-line tools) and ssh into Windows for carrying the build.

> The problem is it's getting ridiculously bloated. On every system I put
> DMD in, I have to extract around 100MB of irrelevant binaries, just to
> then go and delete them (!) or else accumulate 1GB of junk per 10 DMDs.
> On top of all that, it significantly increases both download and
> extraction times.
>
> The problem I don't understand is what's so wrong or problematic with
> having the packaging scripts just generate separate OS archives
> instead of separate OS directories within one archive.

I agree this is a ridiculous situation.


Andrei
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On 5/25/2013 12:14 PM, Nick Sabalausky wrote:
> The problem I don't understand is what's so wrong or problematic with having the packaging scripts just generate separate OS archives instead of separate OS directories within one archive.

The problem is nobody has stepped up to do that. I welcome any help with this.
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On Sat, 25 May 2013 12:38:30 -0700
Walter Bright <walter@digitalmars.com> wrote:

> 
> On 5/25/2013 12:14 PM, Nick Sabalausky wrote:
> > The problem I don't understand is what's so wrong or problematic with having the packaging scripts just generate separate OS archives instead of separate OS directories within one archive.
> 
> The problem is nobody has stepped up to do that. I welcome any help with this.

Has the buildscript been released? My, perhaps outdated, understanding
has been that it isn't available anywhere.
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On 5/25/2013 1:11 PM, Nick Sabalausky wrote:
> On Sat, 25 May 2013 12:38:30 -0700
> Walter Bright <walter@digitalmars.com> wrote:
>
>> On 5/25/2013 12:14 PM, Nick Sabalausky wrote:
>>> The problem I don't understand is what's so wrong or problematic
>>> with having the packaging scripts just generate separate OS
>>> archives instead of separate OS directories within one archive.
>> The problem is nobody has stepped up to do that. I welcome any help
>> with this.
> Has the buildscript been released? My, perhaps outdated, understanding
> has been that it isn't available anywhere.
>

https://github.com/D-Programming-Language/installer


_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On Sat, 25 May 2013 13:34:46 -0700
Walter Bright <walter@digitalmars.com> wrote:

> 
> On 5/25/2013 1:11 PM, Nick Sabalausky wrote:
> > On Sat, 25 May 2013 12:38:30 -0700
> > Walter Bright <walter@digitalmars.com> wrote:
> >
> >> On 5/25/2013 12:14 PM, Nick Sabalausky wrote:
> >>> The problem I don't understand is what's so wrong or problematic with having the packaging scripts just generate separate OS archives instead of separate OS directories within one archive.
> >> The problem is nobody has stepped up to do that. I welcome any help with this.
> > Has the buildscript been released? My, perhaps outdated, understanding has been that it isn't available anywhere.
> >
> 
> https://github.com/D-Programming-Language/installer
> 

I may be overlooking something obvious, but I'm not seeing the part in
there for generating the zip...?
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On 5/25/2013 3:29 PM, Nick Sabalausky wrote:
> On Sat, 25 May 2013 13:34:46 -0700
> Walter Bright <walter@digitalmars.com> wrote:
>
>> On 5/25/2013 1:11 PM, Nick Sabalausky wrote:
>>> On Sat, 25 May 2013 12:38:30 -0700
>>> Walter Bright <walter@digitalmars.com> wrote:
>>>
>>>> On 5/25/2013 12:14 PM, Nick Sabalausky wrote:
>>>>> The problem I don't understand is what's so wrong or problematic
>>>>> with having the packaging scripts just generate separate OS
>>>>> archives instead of separate OS directories within one archive.
>>>> The problem is nobody has stepped up to do that. I welcome any help
>>>> with this.
>>> Has the buildscript been released? My, perhaps outdated,
>>> understanding has been that it isn't available anywhere.
>>>
>> https://github.com/D-Programming-Language/installer
>>
> I may be overlooking something obvious, but I'm not seeing the part in
> there for generating the zip...?

make install
cd phobos
make html
make install
cd ..\doc
make
make install
cd phobos
make install
cd ..\..
cd druntime
make install
cd ..
copy ..\rdmd\dman.exe \dmd2\windows\bin
copy ..\rdmd\rdmd.exe \dmd2\windows\bin
copy ..\rdmd\ddemangle.exe \dmd2\windows\bin
copy ..\VERSION \dmd2\src\

copy \dm\lib\snn.lib \dmd2\windows\lib


\putty\pscp -i \.ssh\colossus.ppk walter@mercury:cbx/mars/dmd32 \dmd2\linux\bin32\dmd
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:cbx/mars/dmd \dmd2\linux\bin64\
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:cbx/mars/phobos/generated/linux/release/32/libphobos2.a \dmd2\linux\lib32
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:cbx/mars/phobos/generated/linux/release/64/libphobos2.a \dmd2\linux\lib64
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:cbx/mars/phobos/generated/linux/release/32/libphobos2.so \dmd2\linux\lib32
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:cbx/mars/phobos/generated/linux/release/64/libphobos2.so \dmd2\linux\lib64

rem \putty\pscp -i \.ssh\colossus.ppk walter@mercury:./bin/shell32 \dmd2\linux\bin32\shell
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:./bin/obj2asm32 \dmd2\linux\bin32\obj2asm
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:./bin/dumpobj32 \dmd2\linux\bin32\dumpobj
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:cbx/rdmd/rdmd32 \dmd2\linux\bin32\rdmd
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:cbx/rdmd/ddemangle32 \dmd2\linux\bin32\ddemangle
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:./bin/dman32 \dmd2\linux\bin32\dman

rem \putty\pscp -i \.ssh\colossus.ppk walter@mercury:./bin/shell \dmd2\linux\bin64
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:./bin/obj2asm \dmd2\linux\bin64
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:./bin/dumpobj \dmd2\linux\bin64
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:cbx/rdmd/rdmd \dmd2\linux\bin64
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:cbx/rdmd/ddemangle \dmd2\linux\bin64
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:./bin/dman \dmd2\linux\bin64

\putty\pscp -i \.ssh\colossus.ppk walter@mercury:./dpl/dmd/docs/man/man1/dmd.1 \dmd2\man\man1\
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:./dpl/dmd/docs/man/man1/dmd.conf.5 \dmd2\man\man1\
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:./dpl/dmd/docs/man/man1/dumpobj.1 \dmd2\man\man1\
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:./dpl/dmd/docs/man/man1/obj2asm.1 \dmd2\man\man1\
\putty\pscp -i \.ssh\colossus.ppk walter@mercury:./dpl/dmd/docs/man/man1/rdmd.1 \dmd2\man\man1\


\putty\pscp -i \.ssh\colossus.ppk walter@goblin:cbx/mars/dmd \dmd2\freebsd\bin32
\putty\pscp -i \.ssh\colossus.ppk walter@goblin:cbx/mars/phobos/generated/freebsd/release/32/libphobos2.a \dmd2\freebsd\lib32

\putty\pscp -i \.ssh\colossus.ppk walter@goblin:/usr/local/bin/shell32 \dmd2\freebsd\bin32\shell
\putty\pscp -i \.ssh\colossus.ppk walter@goblin:/usr/local/bin/obj2asm32 \dmd2\freebsd\bin32\obj2asm
\putty\pscp -i \.ssh\colossus.ppk walter@goblin:/usr/local/bin/dumpobj32 \dmd2\freebsd\bin32\dumpobj
\putty\pscp -i \.ssh\colossus.ppk walter@goblin:cbx/rdmd/rdmd32 \dmd2\freebsd\bin32\rdmd
\putty\pscp -i \.ssh\colossus.ppk walter@goblin:cbx/rdmd/ddemangle32 \dmd2\freebsd\bin32\ddemangle
\putty\pscp -i \.ssh\colossus.ppk walter@goblin:/usr/local/bin/dman32 \dmd2\freebsd\bin32\dman


\putty\pscp -i \.ssh\colossus.ppk ming@pluto:cbx/mars/dmd \dmd2\osx\bin
\putty\pscp -i \.ssh\colossus.ppk ming@pluto:cbx/mars/phobos/generated/osx/release/libphobos2.a \dmd2\osx\lib

\putty\pscp -i \.ssh\colossus.ppk ming@pluto:./bin/shell \dmd2\osx\bin
\putty\pscp -i \.ssh\colossus.ppk ming@pluto:./bin/obj2asm \dmd2\osx\bin
\putty\pscp -i \.ssh\colossus.ppk ming@pluto:./bin/dumpobj \dmd2\osx\bin
\putty\pscp -i \.ssh\colossus.ppk ming@pluto:./bin/dman \dmd2\osx\bin
\putty\pscp -i \.ssh\colossus.ppk ming@pluto:cbx/rdmd/rdmd \dmd2\osx\bin
\putty\pscp -i \.ssh\colossus.ppk ming@pluto:cbx/rdmd/ddemangle \dmd2\osx\bin


pushd \dmzip
make putbeta2
popd


_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On Sat, 25 May 2013 16:21:11 -0700
Walter Bright <walter@digitalmars.com> wrote:

> 
> On 5/25/2013 3:29 PM, Nick Sabalausky wrote:
> > On Sat, 25 May 2013 13:34:46 -0700
> > Walter Bright <walter@digitalmars.com> wrote:
> >
> >> On 5/25/2013 1:11 PM, Nick Sabalausky wrote:
> >>> On Sat, 25 May 2013 12:38:30 -0700
> >>> Walter Bright <walter@digitalmars.com> wrote:
> >>>
> >>>> On 5/25/2013 12:14 PM, Nick Sabalausky wrote:
> >>>>> The problem I don't understand is what's so wrong or problematic with having the packaging scripts just generate separate OS archives instead of separate OS directories within one archive.
> >>>> The problem is nobody has stepped up to do that. I welcome any help with this.
> >>> Has the buildscript been released? My, perhaps outdated, understanding has been that it isn't available anywhere.
> >>>
> >> https://github.com/D-Programming-Language/installer
> >>
> > I may be overlooking something obvious, but I'm not seeing the part in there for generating the zip...?
> 
> make install
> cd phobos
> make html
> make install
> cd ..\doc
> make
> make install
> cd phobos
[...etc...]

Heh, ok, I think I understand the problem ;)

Although I don't think this is important enough to hold up the 2.063 release, I'm going to see what I can do about a cleaned-up version of that script that can go up on github, so we can easily do whatever wrt zips.

Couple questions though:

1. I haven't been closely following the activity/discussions on the matter, but do we have git branches now which all the betas and releases are built directly from? Is it the "staging" branch of each repo?

2. Walter: How in the heck is your working directory structure laid out? I take it the starting point of your script isn't a single directory containing direct checkouts of the "dmd", "phobos", "druntime", "tools", "installer", "dlang.org" projects all as sister directories to each other.

Related note, Something I think may be worth considering for the future:

If we could get simple DMD-bootstrapping scripts into the installer
repo (actually, didn't Andrei already make something like that?), then
all the other scripts could be written in D itself. The big benefit I
see to that is dealing with error conditions, prerequisites, usability,
and multiple platforms (not to mention basic ordinary logic constructs)
is much, much simpler in D than in shell/bash/batch/etc. I wouldn't
mind tackling any or all of that in my spare time if there was interest.
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On 5/25/2013 9:01 PM, Nick Sabalausky wrote:
> Heh, ok, I think I understand the problem ;)

<g>

>
> Although I don't think this is important enough to hold up the 2.063
> release, I'm going to see what I can do about a cleaned-up version
> of that script that can go up on github, so we can easily do whatever
> wrt zips.
>
> Couple questions though:
>
> 1. I haven't been closely following the activity/discussions on the
> matter, but do we have git branches now which all the betas and
> releases are built directly from? Is it the "staging" branch of each
> repo?

The 'staging' thing was discarded. Now, all the repos have a "2.063" branch. When it is released, there will be a "v2.063" tag on that branch. Bug fixes can still be added onto that branch, as well as new point releases as necessary.


>
> 2. Walter: How in the heck is your working directory structure laid
> out? I take it the starting point of your script isn't a single
> directory containing direct checkouts of the "dmd", "phobos",
> "druntime", "tools", "installer", "dlang.org" projects all as sister
> directories to each other.

It's a significantly different structure than on github, as github came much later. But that should be irrelevant to your work.

>
> Related note, Something I think may be worth considering for the
> future:
>
> If we could get simple DMD-bootstrapping scripts into the installer
> repo (actually, didn't Andrei already make something like that?), then
> all the other scripts could be written in D itself. The big benefit I
> see to that is dealing with error conditions, prerequisites, usability,
> and multiple platforms (not to mention basic ordinary logic constructs)
> is much, much simpler in D than in shell/bash/batch/etc. I wouldn't
> mind tackling any or all of that in my spare time if there was interest.

I think that's a cool idea.
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta