FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > ArchLinux > ArchLinux Pacman Development

 
 
LinkBack Thread Tools
 
Old 07-16-2008, 12:15 AM
Dan McGee
 
Default Remove pacman.static build from build files

This presents plenty of problems on OSes besides Linux, and even on Linux
when the libtool file for libarchive isn't present. The static build isn't
all that useful anyway as missing something such as glibc will still leave
you unable to run the pacman.static binary. Remove it from the formal build
process.

Signed-off-by: Dan McGee <dan@archlinux.org>
---
configure.ac | 16 ----------------
src/pacman/.gitignore | 2 --
src/pacman/Makefile.am | 7 -------
3 files changed, 0 insertions(+), 25 deletions(-)

diff --git a/configure.ac b/configure.ac
index ab5a374..b4b6a56 100644
--- a/configure.ac
+++ b/configure.ac
@@ -119,11 +119,6 @@ AC_ARG_ENABLE(git-version,
[enable use of git version in version string if available]),
[wantgitver=$enableval], [wantgitver=no])

-# Help line for pacman.static
-AC_ARG_ENABLE(pacman-static,
- AS_HELP_STRING([--disable-pacman-static], [do not build static version of pacman]),
- [pacmanstatic=$enableval], [pacmanstatic=yes])
-
# Checks for programs.
AC_PROG_AWK
AC_PROG_CC_C99
@@ -324,16 +319,6 @@ else
fi
AM_CONDITIONAL(USE_GIT_VERSION, test "x$usegitver" = "xyes")

-# Enable or disable inclusion of pacman.static
-AC_MSG_CHECKING(whether to build pacman.static)
-if test "x$pacmanstatic" = "xyes" ; then
- AC_MSG_RESULT(yes)
- AC_DEFINE([INCLUDE_PACMAN_STATIC], , [Build pacman.static])
-else
- AC_MSG_RESULT(no)
-fi
-AM_CONDITIONAL(INCLUDE_PACMAN_STATIC, test "x$pacmanstatic" = "xyes")
-
# Set root directory
AC_SUBST(ROOTDIR)
# Set package file extension
@@ -398,7 +383,6 @@ ${PACKAGE_NAME}:
Doxygen support : ${usedoxygen}
Asciidoc support : ${useasciidoc}
debug support : ${debug}
- build pacman.static : ${pacmanstatic}
"

# vim:set ts=2 sw=2 noet:
diff --git a/src/pacman/.gitignore b/src/pacman/.gitignore
index c47851c..6a358aa 100644
--- a/src/pacman/.gitignore
+++ b/src/pacman/.gitignore
@@ -2,5 +2,3 @@
.libs
pacman
pacman.exe
-pacman.static
-pacman.static.exe
diff --git a/src/pacman/Makefile.am b/src/pacman/Makefile.am
index e5f8cb3..220ee9c 100644
--- a/src/pacman/Makefile.am
+++ b/src/pacman/Makefile.am
@@ -6,10 +6,6 @@ logfile = ${localstatedir}/log/pacman.log

bin_PROGRAMS = pacman

-if INCLUDE_PACMAN_STATIC
-bin_PROGRAMS += pacman.static
-endif
-
DEFS = -DLOCALEDIR="@localedir@"
-DCONFFILE="$(conffile)"
-DROOTDIR="$(ROOTDIR)"
@@ -40,7 +36,4 @@ pacman_SOURCES =

LDADD = $(LTLIBINTL) $(top_builddir)/lib/libalpm/.libs/libalpm.la

-pacman_static_SOURCES = $(pacman_SOURCES)
-pacman_static_LDFLAGS = $(LDFLAGS) -all-static
-
# vim:set ts=2 sw=2 noet:
--
1.5.6.2


_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 07-16-2008, 01:23 AM
Allan McRae
 
Default Remove pacman.static build from build files

Dan McGee wrote:
> This presents plenty of problems on OSes besides Linux, and even on Linux
> when the libtool file for libarchive isn't present. The static build isn't
> all that useful anyway as missing something such as glibc will still leave
> you unable to run the pacman.static binary. Remove it from the formal build
> process.
>

I didn't realize that is was not very static. But is this not useful
for people who want to try and upgrade their really old systems? I
suppose if they can't get pacman going in the first place then they will
be reasonably screwed with the rest of the upgrade.



_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 07-16-2008, 01:32 AM
"Dan McGee"
 
Default Remove pacman.static build from build files

On Tue, Jul 15, 2008 at 8:23 PM, Allan McRae <allan@archlinux.org> wrote:
> Dan McGee wrote:
>> This presents plenty of problems on OSes besides Linux, and even on Linux
>> when the libtool file for libarchive isn't present. The static build isn't
>> all that useful anyway as missing something such as glibc will still leave
>> you unable to run the pacman.static binary. Remove it from the formal build
>> process.
>>
>
> I didn't realize that is was not very static. But is this not useful
> for people who want to try and upgrade their really old systems? I
> suppose if they can't get pacman going in the first place then they will
> be reasonably screwed with the rest of the upgrade.

Yeah, I think it has always been one of those "I hope it works" type
things. In any case, I think this is more appropriate for the pacman
PKGBUILD if we truely want a static build, rather than in the pacman
buildchain.

If you really want to test the "screwing up" stuff, boot up Simo's
live CD installer and do a pacman -R glibc, and see how functional the
system is. You'll note that pacman.static is pretty bunk at that
point.

-Dan

_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 

Thread Tools




All times are GMT. The time now is 06:20 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org