Author: pierre
Date: Sat Mar 11 08:47:43 2017
New Revision: 3908
Log:
Update pacman commands (not version, it would require too many changes to the
build system).
Modified:
jhalfs/trunk/README.PACKAGE_MANAGEMENT
jhalfs/trunk/pkgmngt/packageManager.xml.pacman
Modified: jhalfs/trunk/README.PACKAGE_MANAGEMENT
==============================================================================
--- jhalfs/trunk/README.PACKAGE_MANAGEMENT Fri Mar 10 12:42:08 2017
(r3907)
+++ jhalfs/trunk/README.PACKAGE_MANAGEMENT Sat Mar 11 08:47:43 2017
(r3908)
@@ -5,14 +5,14 @@
There are several hints discussing package management for LFS, but
nothing under jhalfs. There used to be a patch for PACO that I cannot
- find now. This is a modification, which allows to use a package manager
- inside jhalfs. I hope it is flexible enough to support several package
- managers. My implementation uses dpkg, from Debian, in a very crude way.
- Debian has a sophisticated package management system, which I have not
- tried to use here. For example, it should be usable with Pacman from
- Arch Linux (http://www.archlinux.org), as far as I remember from my old
- days with DIYL. I am sorry to say I have (almost) no experience with
- rpm, so I cannot tell whether it would fit.
+ find now. This is a modification ("DESTDIR install" automation), which
+ allows to use a package manager inside jhalfs. I hope it is flexible enough
+ to support several package managers, at least among those who use DESTDIR
+ install. My initial implementation used dpkg, from Debian, in a very
+ crude way (Debian has a sophisticated package management system, which
+ I have not tried to use here). There is also a port to Pacman from
+ Arch Linux (http://www.archlinux.org). I am sorry to say I have (almost)
+ no experience with rpm, so I cannot tell whether it would fit.
2. OVERVIEW OF THE SYSTEM:
@@ -56,4 +56,6 @@
upgrade. The user has to write his own `packInstall' function. The shell
function should be defined in a file named `packInstall.sh', residing in
the `pkgmngt' directory. A template is provided, as well as two example
- scripts for dpkg and pacman.
+ scripts for dpkg and pacman. Note that, due to the way pacman checks the
+ available space on disk, the root directory in chroot must be a mount point,
+ otherwise the installation of packages fails.
Modified: jhalfs/trunk/pkgmngt/packageManager.xml.pacman
==============================================================================
--- jhalfs/trunk/pkgmngt/packageManager.xml.pacman Fri Mar 10 12:42:08
2017 (r3907)
+++ jhalfs/trunk/pkgmngt/packageManager.xml.pacman Sat Mar 11 08:47:43
2017 (r3908)
@@ -22,7 +22,7 @@
<para>MD5 sum:
<literal>e9aa6dec29920eba8ef706ea5823bad7</literal></para>
<para>Download: <ulink
url="http://www.libarchive.org/downloads/libarchive-3.1.2.tar.gz"/></para>
<para>MD5 sum:
<literal>efad5a503f66329bb9d2f4308b5de98a</literal></para>
- <para>Download: <ulink
url="ftp://ftp.archlinux.org/other/pacman/pacman-4.1.2.tar.gz"/></para>
+ <para>Download: <ulink
url="https://sources.archlinux.org/other/pacman/pacman-4.1.2.tar.gz"/></para>
<para>MD5 sum:
<literal>063c8b0ff6bdf903dc235445525627cd</literal></para>
</sect1>
@@ -43,6 +43,7 @@
<sect2 role="installation">
<screen><userinput remap="configure">./configure --prefix=/tools \
--without-bz2lib \
+ --without-xml2 \
--enable-bsdtar=static \
--enable-bsdcpio=static</userinput></screen>
<screen><userinput remap="make">make</userinput></screen>
@@ -75,6 +76,7 @@
remap attribute are considered configuration instructions and executed last.
You
can also use remap="adjust" for the same purpose. -->
<screen><userinput remap="configure">./configure --prefix=/tools \
+ --without-openssl \
PKG_CONFIG_PATH=/tools/lib/pkgconfig \
DUPATH=/tools/bin/du</userinput></screen>
--
http://lists.linuxfromscratch.org/listinfo/alfs-log
Unsubscribe: See the above information page
