<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 18, 2013 at 11:01 PM, luke.leighton <span dir="ltr"><<a href="mailto:luke.leighton@gmail.com" target="_blank">luke.leighton@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, Sep 18, 2013 at 5:03 PM, joem <<a href="mailto:joem@martindale-electric.co.uk">joem@martindale-electric.co.uk</a>> wrote:<br>
> On Wed, 2013-09-18 at 15:30 +0000, Derek wrote:<br>
>> joem <joem <at> <a href="http://martindale-electric.co.uk" target="_blank">martindale-electric.co.uk</a>> writes:<br>
><br>
>> > > Joe, you must specify your goal more clearly. So I'll ask once again:<br>
>> > ><br>
>> > > Do you want to recreate a Linaro ALIP image all the way from sources?<br>
>> > ><br>
>> > ><br>
>> > The goal is to create the freedom to distribute working bootable Linux<br>
>> > distro binary images with tool chain ready to be used as soon as it is<br>
>> > unzipped and dd'd into a SD card or a sata drive and satisfy the GPL.<br>
>> ><br>
>> > $$$$ Krsching!! $$$<br>
>><br>
>> Joe,<br>
>> I don't think I get it. Right now, to create a bootable SD card, I'd<br>
>> partition it, load a kernel and fex, and debootstrap Debian into a root<br>
>> directory. What I'd need would be a list of packages, such as "basic",<br>
>> "development", or "desktop". I don't think I'd be happy putting 100GB on an<br>
>> SD card, just to run a basic router.<br>
><br>
><br>
> The issue was that I was releasing binaries uSD cards<br>
> because my way of doing things is that I believe tools are more<br>
> important than recipes. It takes all sorts to make the world go around,<br>
> and that is where I stand on the importance of binaries.<br>
><br>
><br>
> Then gpl gets in the way and says, though my intentions are good,<br>
> in describing how the binary was built, its not good enough,<br>
> I (not some 3rd party) must supply the exact sources for all items in<br>
> the binary and working tools.<br>
><br>
><br>
> When I release the 2GB uSD Card binary bootable distro for eoma,<br>
> I am obliged to supply the exact sources for each item that has a gpl<br>
> license.<br>
<br>
</div></div> ... or you are obliged to provide a pointer to where the sources can<br>
be obtained: that is sufficient. you *don't* have to host them<br>
yourself... but you *do* have to ensure that you've provide the full<br>
set of links to sources, full set of links to all tools and scripts.<br>
a full set of instructions is also nice but not strictly necessary.<br>
however having those instructions is a good idea because it allows<br>
*you* to ensure that you have the full set of sources (or links to)<br>
right and the full set of tools (or links to tools) also correct.<br>
<div class="im"><br>
<br>
> I also intend to distribute soon a uSD binary with ubuntu 12.04.3 with<br>
> toolchain and everything set up for eoma development.<br>
><br>
><br>
> So I at some time in the future will put together all the sources as a<br>
> link to download the 100GB odd of all the sources that went into making<br>
> the exact same binaries as I am distributing. So you don't need to<br>
> download the sources if you don't want to.<br>
><br>
> Just enjoy the 2Gb binaries as they are and make the router happen now!!<br>
><br>
> Its just that if I am the one distributing the binary, I must also<br>
> distribute the exact sources. And I will do it, because that is the<br>
> only way to guarantee others can also distribute binaries and produce<br>
> the sources on demand.<br>
><br>
> At the moment this responsibility is being shrugged off by a lot<br>
> of factories that make products, or is being passed on to others<br>
> when you load up a recipe for building a bootable uSD card.<br>
> It drains their time, your time, and creates support issues.<br>
> (The last things you want draining life out of product before it<br>
> is even born!)<br>
><br>
<br>
<br>
</div><div class="im">>> The best thing, I think, would be getting the 3.4 kernel patches to go from<br>
>> debian-standard to sunxi-lkcl-whatever as a debian package, making your<br>
>> "build and install" script as easy as 'apt-get linux-image-watcha'<br>
>><br>
>> soo... why fork a distro?<br>
>><br>
<br>
</div> ... because he doesn't understand what he's doing, arokux.<br></blockquote><div>That was not me :p <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
and, also, he has an additional requirement to his clients to provide<br>
10-20 year lifecycles for all software.<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
<a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br>
</div></div></blockquote></div><br></div></div>