On Mon, 2010-09-27 at 09:44 +0200, Alexander Sack wrote:
> On Thu, Sep 23, 2010 at 8:42 PM, Guilherme Salgado
> wrote:
> > a) unpack the binary tarball to a tmp dir, install the hwpack (which
> > may cause lots of data to be written) and then move that to the SD card
> > or
> > b) unpack the tar
On Thu, Sep 23, 2010 at 8:42 PM, Guilherme Salgado
wrote:
> a) unpack the binary tarball to a tmp dir, install the hwpack (which
> may cause lots of data to be written) and then move that to the SD card
> or
> b) unpack the tarball straight into the sd card (as is done currently)
> and then inst
On Thu, 23 Sep 2010 15:42:34 -0300, Guilherme Salgado
wrote:
> Hi,
>
> I've recently changed l-m-c to take an hwpack, which is installed before
> the image is built. To keep that change simple I had to unpack the
> binary tarball into a tmp directory, install the hwpack, repack the
> tarball an
Hi,
I've recently changed l-m-c to take an hwpack, which is installed before
the image is built. To keep that change simple I had to unpack the
binary tarball into a tmp directory, install the hwpack, repack the
tarball and then continue with the image generation. This extra
unpacking/repacking
Hi,
I've recently changed l-m-c to take an hwpack, which is installed before
the image is built. To keep that change simple I had to unpack the
binary tarball into a tmp directory, install the hwpack, repack the
tarball and then continue with the image generation. This extra
unpacking/repacking
