Sender: =?UTF-8?Q?Timo_Ter=C3=A4s?= <timo.teras@gmail.com>
Date: Wed, 28 Oct 2015 18:17:56 +0200
From: Timo Teras <timo.teras@iki.fi>
To: alpine-devel@lists.alpinelinux.org
Subject: [alpine-devel] apk-tools ideas
Message-ID: <20151028181756.4715b37c@vostro>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,

Another ideas collection mail for post-3.3 time; this time for
apk-tools.

My ideas box has following items:

- Support 'bare' root. The idea is to have boot-media managed by
  apk-tools, and be upgradeable using apk. It'd technically be one .apk
  that can be upgraded from fixed URL. Something like
  "apk --root /media/boot upgrade" or so. Of course alpine-iso / abuild
  would need to support creating boot images in compatible format. They
  should also support creating boot-media / firmware package by giving
  in an apkovl for easy roll out of appliances. But that's another
  story.

- Potentially update the package format to use pax-headers instead
  of .PKGINFO and .SIGN.* meta-data files. This would allow extraction
  with tar and there would be no extra files extracted.

- Rework "repositories" file so that it apk config manages $MIRROR and
  $BRANCH. So upgrading branch/changing mirror changes config file, not
  the repository config. Similar to apt sources.list format.

- Elliptic Curve signature support

- Tracking what services to restart after upgrade, see:
  http://bugs.alpinelinux.org/issues/2251
  Though, migrating to s6-rc was also in the discussion so that might
  affect things if it happens.

- Merging of pre/post and install/upgrade scripts to single script

- Have apk add users/groups from .PKGINFO meta data instead of
  requiring scripts for that

and few other more of minor bug fix issues.

Any other ideas? Or comments on the priorities?

/Timo


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---