Date: Wed, 3 Jul 2013 10:34:17 -0400
From: Dubiousjim <dubiousjim@gmail.com>
To: alpine-devel@lists.alpinelinux.org
Subject: [alpine-devel] abuild git repo question
Message-ID: <20130703143417.GG1550@zen>
Mail-Followup-To: alpine-devel@lists.alpinelinux.org
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)

Looking at the Makefile inside the abuild git repo, I see a target
"dist", which rolls up a source repository. However, I guess we're
actually not using "make dist", because what that target rolls up is incomplete
(it omits abuild-tar.c abuild-sudo.c functions.sh aports.lua, which
are all required to "make install"). Also, what actually gets downloaded
if you go to $APORTS/main/abuild and do "abuild fetch" includes
.gitignore and so on.

Q1. I have to tinker with the Makefile anyway in some patches I'll be
sending. Should I add the missing files to the dist target?

There are a lot of files in the abuild git repo that aren't installed,
and I think at least some of them are cruft. Perhaps others are
work-in-progress.

bootchartd and initramfs-init seem to lag behind the versions in the
mkinitfs repo, which are what we actually install.

Perhaps these files are also cruft:
 APKBUILD-svn.proto
 alpine.mk
 alpine.packages
 cmp-apks-iso
 mkinitram
 mkmodloop

I'm not sure if apkbuild-pypi.in is cruft or work-in-progress.

Q2. Shall we "git rm" some of these files?

-- 
Dubiousjim
dubiousjim@gmail.com


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---