public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Pakfire3 running on IPFire 2
Date: Thu, 18 Oct 2012 18:57:12 +0200	[thread overview]
Message-ID: <508034E8.6000508@ipfire.org> (raw)
In-Reply-To: <1350571249.9815.116.camel@rice-oxley.tremer.info>

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

Hello Michael,

I've attached you a Diff-File with the changes from the developer 
summit, to build and use pakfire3 on an IPFire 2 system.

Best regards,

Stefan
> Hello,
>
> Erik and Stefan, you have been working on getting pakfire 3 working on
> IPFire 2, recently.
>
> I tried to build it today just for my little testing games and there are
> still (at least) two requirements missing: elfutils and beecrypt.
>
> So the question is: Did you disable parts of the package so you won't
> need those two or did I miss to merge a patch you sent me?
>
> I would like to have pakfire3 as a regular package in IPFire 2, because
> a lot of people would like to use IPFire 2 as a build platform for
> IPFire 3. Setting up an other box with some mainstream distro is just
> extra work.
>
> Michael
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
>


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: pakfire3-changes-for-ipfire2.diff --]
[-- Type: text/x-patch, Size: 1026 bytes --]

diff --git a/Makefile b/Makefile
index 0361af6..0bcb1bf 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
 
 include Makeconfig
 
-SUBDIRS = po python tools tools/fake-environ
+SUBDIRS = python tools tools/fake-environ
 
 all: build
 
diff --git a/tools/Makefile b/tools/Makefile
index d7cbf70..499beb4 100644
--- a/tools/Makefile
+++ b/tools/Makefile
@@ -12,7 +12,7 @@ LIBS_POPT = -lpopt
 
 SCRIPTS = $(SCRIPTS_BIN) $(SCRIPTS_SHELL)
 SCRIPTS_BIN   = \
-	debugedit
+	#debugedit
 
 SCRIPTS_SHELL = \
 	chroot-shell \
@@ -50,7 +50,7 @@ install: $(SCRIPTS)
 
 	# Create script aliases.
 	-mkdir -pv $(DESTDIR)/usr/bin
-	ln -svf ../..$(SCRIPT_DIR)/pakfire-multicall.py $(DESTDIR)/usr/bin/pakfire
+	ln -svf ../..$(SCRIPT_DIR)/pakfire-multicall.py $(DESTDIR)/usr/bin/pakfire3
 	ln -svf ../..$(SCRIPT_DIR)/pakfire-multicall.py $(DESTDIR)/usr/bin/pakfire-builder
 	ln -svf ../..$(SCRIPT_DIR)/pakfire-multicall.py $(DESTDIR)/usr/bin/pakfire-client
 	ln -svf ../..$(SCRIPT_DIR)/pakfire-multicall.py $(DESTDIR)/usr/bin/pakfire-daemon

  reply	other threads:[~2012-10-18 16:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 14:40 Michael Tremer
2012-10-18 16:57 ` Stefan Schantl [this message]
2012-10-18 20:54   ` Michael Tremer

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=508034E8.6000508@ipfire.org \
    --to=stefan.schantl@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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