X-Original-To: alpine-devel@lists.alpinelinux.org
Delivered-To: alpine-devel@mail.alpinelinux.org
Received: from ironport2-out.teksavvy.com (ironport2-out.teksavvy.com [206.248.154.183])
	by mail.alpinelinux.org (Postfix) with ESMTP id A298ADC1A2A
	for <alpine-devel@lists.alpinelinux.org>; Mon, 26 Mar 2012 19:54:45 +0000 (UTC)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFAKU/KE9MCqMW/2dsb2JhbACBX5x7eYhwnhmGGQSUToZLhAk
X-IronPort-AV: E=Sophos;i="4.73,1,1325480400"; 
   d="scan'208";a="170199954"
Received: from 76-10-163-22.dsl.teksavvy.com (HELO waltdnes.org) ([76.10.163.22])
  by ironport2-out.teksavvy.com with SMTP; 26 Mar 2012 15:54:44 -0400
Received: by waltdnes.org (sSMTP sendmail emulation); Mon, 26 Mar 2012 15:53:49 -0400
From: "Walter Dnes" <waltdnes@waltdnes.org>
Date: Mon, 26 Mar 2012 15:53:49 -0400
To: Alpine devel <alpine-devel@lists.alpinelinux.org>
Subject: Re: [alpine-devel] Questions about doing a glibc-based build
Message-ID: <20120326195349.GA1089@waltdnes.org>
References: <20120325211042.GA29428@waltdnes.org>
 <1332710453.21718.140661053914881.0D2AE04A@webmail.messagingengine.com>
X-Mailinglist: alpine-devel
Precedence: list
List-Id: Alpine Development <alpine-devel.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-devel+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-devel@lists.alpinelinux.org>
List-Help: <mailto:alpine-devel+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-devel+subscribe@lists.alpinelinux.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1332710453.21718.140661053914881.0D2AE04A@webmail.messagingengine.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Sun, Mar 25, 2012 at 05:20:53PM -0400, Dubiousjim wrote

> Hi Walter, I've not attempted this. In fact, I've just started using
> Alpine myself. However, I have been spending a lot of time in the wiki
> recently, doing some cleanup there as a way to learn how this distro is
> organized.
> 
> So I know that there is this page:
> http://wiki.alpinelinux.org/wiki/Running_glibc_programs
> 
> Perhaps that's a good place to start.

  That's not quite what I'm looking for.  I don't want a glibc chroot
inside of a uclibc Alpine.  I'd like to rebuild Alpine with glibc
replacing uclibc.  That would probably mean going to the git sources,
making my own modified copy and building from there.  Since I'm not a
programmer, let alone a developer, that's going to be rather difficult.

  Alpine looks like it could be a functional, lightweight, mdev-based,
end-user distro if only glibc could be dropped in in place of uclibc.

  I have one more question.  Is Alpine source-based or binary?
According to
http://wiki.alpinelinux.org/wiki/Comparison_with_Gentoo_and_Debian

> Note that Gentoo is source based, just like ports in FreeBSD is while
> Debian uses pre-compiled binaries.  Alpine is compiled using Gentoo
> portage but Alpine itself uses its own apk-tools binary package that
> are more similar FreeBSD's binary packages.

  That's rather vague, and I'd like an English translation <G>.

  I have looked at LFS (Linux From Scratch) but they're already at
udev-181.

-- 
Walter Dnes <waltdnes@waltdnes.org>


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---