From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (71-34-83-176.ptld.qwest.net [71.34.83.176]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 0BD7779B8A for ; Wed, 11 Mar 2015 05:58:51 -0700 (PDT) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20150205111024.eklhad@comcast.net> <20150306202823.GC15732@toaster.adamthompson.me.uk> <87385h6cc5.fsf@mushroom.localdomain> <20150309224454.GA17294@toaster.adamthompson.me.uk> Date: Wed, 11 Mar 2015 05:58:39 -0700 In-Reply-To: <20150309224454.GA17294@toaster.adamthompson.me.uk> (Adam Thompson's message of "Mon, 9 Mar 2015 22:44:54 +0000") Message-ID: <87zj7j1yio.fsf@mushroom.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] freak attack X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 12:58:52 -0000 Adam Thompson writes: > I wonder if we need an automated system to rebuild these if we don't have one > already? Well, we definitely don't have one already. Here's what I do. I have a couple qemu hard disk images of Alpine Linux: one for i686 and one for x86_64. Alpine doesn't package a static readline library, and in fact, I don't think there's a clean way to build it in their ports system. But I'm a persistent fellow; I made static readline build for me. I also had to build Spidermonkey from source. So that's my infrastructure. I have a slightly customized makefile for building the static binaries, since the linker invocation requires that I specify a bunch of additional libraries that are pulled in automatically when linking dynamically. So now it's basically a matter of: 1. Booting my virtual machines, 2. Insuring that their system libraries are all up to date, 3. Building edbrowse and taring up the resultant binaries [1] 4. Copying them to my development machine 5. Signing the tar files with gpg 6. Uploading them to my web server. Most of that can be automated, with the possible exception of step 2. Is it worth the trouble? Maybe not right now. But it's definitely worth the 10 minutes it took me to document it, because if I get hit by a bus or something, you guys can recreate my process if you want. -- Chris