From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package: add pacman 4.2.1
Date: Fri, 20 Mar 2015 08:15:53 +0200 [thread overview]
Message-ID: <20150320061553.GE25388@tarshish> (raw)
In-Reply-To: <1426736888-29437-5-git-send-email-steven@uplinklabs.net>
Hi Steven,
On Wed, Mar 18, 2015 at 08:48:07PM -0700, Steven Noonan wrote:
> diff --git a/package/pacman/Config.in b/package/pacman/Config.in
> new file mode 100644
> index 0000000..9c4ca66
> --- /dev/null
> +++ b/package/pacman/Config.in
> @@ -0,0 +1,18 @@
> +config BR2_PACKAGE_PACMAN
> + bool "pacman"
> + depends on BR2_TOOLCHAIN_USES_GLIBC
Why? Please explain in the commit log.
> + select BR2_PACKAGE_LIBGPGME
> + select BR2_PACKAGE_LIBARCHIVE
> + select BR2_PACKAGE_LIBCURL
> + select BR2_PACKAGE_OPENSSL
Please propagate dependencies.
> + help
> + Pacman is the package manager used by the Arch distribution. It is a
> + frontend for the ALPM (Arch Linux Package Management) library.
> +
> + Pacman does not strive to "do everything." It will add, remove and
> + upgrade packages in the system, and it will allow you to query the
> + package database for installed packages, files and owners. It also
> + attempts to handle dependencies automatically and can download
> + packages from a remote server. Arch packages are simple archives, with
> + .pkg.tar.gz extension for binary packages and .src.tar.gz for source
> + packages.
> diff --git a/package/pacman/pacman.mk b/package/pacman/pacman.mk
> new file mode 100644
> index 0000000..e979adb
> --- /dev/null
> +++ b/package/pacman/pacman.mk
> @@ -0,0 +1,14 @@
> +################################################################################
> +#
> +# pacman
> +#
> +################################################################################
> +
> +PACMAN_VERSION = 4.2.1
> +PACMAN_SITE = https://sources.archlinux.org/other/pacman
> +PACMAN_SOURCES = pacman-$(PACMAN_VERSION).tar.gz
Default.
> +PACMAN_DEPENDENCIES = glibc libarchive libcurl libgpgme openssl
No need to explicitly depend on 'glibc'. glibc is part of the toolchain that
is an implicit dependency of everything.
> +PACMAN_LICENSE = GPLv2
> +PACMAN_LICENSE_FILES = COPYING
> +
> +$(eval $(autotools-package))
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-03-20 6:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 3:48 [Buildroot] [PATCH] package: add hwloc 1.10.1 Steven Noonan
2015-03-19 3:48 ` [Buildroot] [PATCH] package: add powertop 2.7 Steven Noonan
2015-03-19 5:31 ` Baruch Siach
2015-03-19 3:48 ` [Buildroot] [PATCH] package: add shadow 4.2.1 Steven Noonan
2015-03-19 13:07 ` Ryan Barnett
2015-07-18 20:11 ` Thomas Petazzoni
2015-03-19 3:48 ` [Buildroot] [PATCH] package/numactl: upgrade to 2.0.10 Steven Noonan
2015-03-19 5:26 ` Baruch Siach
2015-03-19 5:30 ` Steven Noonan
2015-03-19 3:48 ` [Buildroot] [PATCH] package: add pacman 4.2.1 Steven Noonan
2015-03-20 6:15 ` Baruch Siach [this message]
2015-03-20 19:52 ` Thomas Petazzoni
2015-03-20 20:18 ` Steven Noonan
2015-03-20 20:34 ` Thomas Petazzoni
2015-03-20 21:19 ` Steven Noonan
2015-03-19 3:48 ` [Buildroot] [PATCH] package: add mosh 1.2.4 Steven Noonan
2015-03-20 6:12 ` Baruch Siach
2015-03-19 5:21 ` [Buildroot] [PATCH] package: add hwloc 1.10.1 Baruch Siach
2015-03-19 5:24 ` Steven Noonan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150320061553.GE25388@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox