DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=nJDF+Dg3qaygIhlRYdWYG5NKv7JN+Nq0X50OPwrLK116COch+jHHi83+iVKtUmf7KO
         8TwxQkAbDM4HpQDAvmlUrxchzEJDUJ+uSu1uSNa8SqeJL6Pr2HSWwU2r8YTagsIZ/nrD
         L3HbpzsFAZA1zkSFgVgig5Yxf0k96fA8dWTZI=
Precedence: list
MIME-Version: 1.0
In-Reply-To: <1283783140.26584.360.camel@ncopa-desktop.nor.wtbts.net>
References: <1283783140.26584.360.camel@ncopa-desktop.nor.wtbts.net>
Date: Mon, 6 Sep 2010 18:07:00 +0200
Message-ID: <AANLkTi=mGOKKQtapn+NgQtcr+AV=Mx+HDkuN45YadPxs@mail.gmail.com>
Subject: Re: [alpine-devel] how to skip packages in aports tree and support
 for eglibc
From: Carlo Landmeter <clandmeter@gmail.com>
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: Alpine Development <alpine-devel@lists.alpinelinux.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

On Mon, Sep 6, 2010 at 4:25 PM, Natanael Copa <ncopa@alpinelinux.org> wrote=
:
> Hi,
>
> Carlo have been working on building an eglibc based alpine and afaik he
> has the bootstrapping of the toolchain more or less working.
>

For anybody who is interested to get started i have a repo here (its i686):

http://alpine.nethq.org/clandmeter/eglibc/

My current tree can be found here:

http://git.alpinelinux.org/cgit/aports-clandmeter/?h=3Deglibc

Not much has be be changed to make it work. Just add the following
vars to your abuild.conf when you want to start building:

BUILD_BASE=3D"binutils gcc make patch eglibc-dev g++"
ALPINE_LIBC=3D"eglibc"

> Now, the question is, how do we handle the build trees?
>
> I think that best would be that we have same tree for all libcs and
> archs. Then we could have conditional dependencies, something like:
>
> # dont use libiconv if eglibc
> if ! [ "$ALPINE_LIBC" =3D "eglibc" ]; then
> =A0 =A0 =A0 =A0makedepends=3D"$makedepends libiconv-dev"
> fi
>

I am not sure if this is possible, but could we move this logic into
abuild and make something like:

makedepends=3D"libiconv-dev:uclibc zlib-dev"

> Similar we could have conditionals for different arch specifics.
>
> Now, there might be some packages that does not make sense build at all.
> For example, we dont want build eglibc on a uclibc system at all since
> it doesnt make sense to build it.
>
> The question is how, do we disable it?
>
> Same goes for different arch specific packages. I think for archs we
> could in the APKBUILD do something like:
>
> arch=3D"x86 x86_64 mips"
>
> But how do we do with uclibc/eglibc? do we have a separarate libc
> variable?
>
> libc=3D"uclibc eglibc"

This looks to be the correct way to do it if we look at other distributions=
.

>
> Alternatively we could keep them in separate branches and do git tricks
> to merge the common commits, but I'd prefer have them joined if
> possible.
>
> Other ideas?
>
> -nc
>
>
>
>
> ---
> Unsubscribe: =A0alpine-devel+unsubscribe@lists.alpinelinux.org
> Help: =A0 =A0 =A0 =A0 alpine-devel+help@lists.alpinelinux.org
> ---
>
>


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---