PKGBUILD for unsermake has patch..not recognized

lilsirecho · 2007-11-12 00:34:16

The patch is in the same directory but the makepkg reports cannot find patch...

lilsirecho · 2007-11-14 03:42:11

bump

elasticdog · 2007-11-14 03:56:21

Can you post the PKGBUILD?

lilsirecho · 2007-11-14 04:21:46

Elastic Dog;

# Contributor: Darwin Bautista <djclue917@gmail.com>

pkgname=unsermake-svn
pkgver=661033
pkgrel=1
pkgdesc="A replacement for automake"
arch=('i686' 'x86_64')
url="http://wiki.kde.org/tiki-index.php?page=unsermake"
license=('GPL')
depends=('python>=2.5')
makedepends=('subversion')
provides=('unsermake')
conflicts=('unsermake')
source=(unsermake-python25.patch)
md5sums=('18e55a3d7838e2b04e6a7c79e07df947')

_svntrunk=svn://anonsvn.kde.org/home/kde/trunk/kdenonbeta
_svnmod=unsermake

build() {
# Checkout SVN repository
msg "Checking out SVN repository..."
svn co ${_svntrunk}/${_svnmod}@${pkgver} --config-dir ./ -r ${pkgver} ${_svnmod}
msg "SVN checkout finished or server timed out..."

cd ${startdir}/src/unsermake/

patch -Np1 -i ../unsermake-python25.patch || return 1
install -D -m755 unsermake ${startdir}/pkg/usr/bin/unsermake

mkdir -p ${startdir}/pkg/usr/lib/python2.5/site-packages/unsermake
install -m644 *.py *.um ${startdir}/pkg/usr/lib/python2.5/site-packages/unsermake/
}

EDIT------------------------------------------------------------------------------------------------------------------

Patch:::::::::::::::::::::::
--- unsermake-20060706.orig/unsermake 2006-07-07 01:07:51.000000000 +0800
+++ unsermake-20060706/unsermake 2007-07-24 11:35:39.000000000 +0800
@@ -1,16 +1,12 @@
-#! /bin/sh
+#!/bin/bash

-self="$0"
-if test -L "$self"; then
- try=`readlink $self 2>/dev/null` && self=$try
-fi
-mods=`dirname $self`
-directory=`dirname $mods`
-mod=`basename $mods`
+mods=/usr/lib/python2.5/site-packages/unsermake
+directory=/usr/lib/python2.5/site-packages/unsermake
+mod=unsermake
if test -n "$PYTHONPATH"; then
export PYTHONPATH=$directory:$PYTHONPATH
else
export PYTHONPATH=$directory
fi
-exec python -c "import $mod; $mod.main()" --modules $mods "$@"
+exec python2.5 -c "import $mod; $mod.main()" --modules $mods "$@"

Last edited by lilsirecho (2007-11-14 04:27:53)

lilsirecho · 2007-11-14 16:08:30

Bump

elasticdog · 2007-11-14 16:25:15

Just from looking at the PKGBUILD, I'd say it's because you never did "cd $stardir/src" at the beginning of the build, and your patch command then looks in the parent directory, which of course, is not the correct location.

Last edited by elasticdog (2007-11-14 16:25:34)

lilsirecho · 2007-11-14 17:10:19

My understanding of PKGBUILD and makepkg has been that it performs within the directory that holds all the data.

I have been mistaken about the use of PKGBUILD therefore since it doesn't always "makepkg" directly from the PKGBUILD script.......

Thanx for the info!!!

lilsirecho · 2007-11-14 17:24:54

The pkgbuild shows the following:

cd #{startdir}/src/unsermake

What is meant by the term {startdir}?

When is this entry made? The makepkg stops at ....File to patch.... Is it here that I enter the cd$,etc?

lilsirecho · 2007-11-14 17:40:37

bump

lilsirecho · 2007-11-14 18:19:15

bump

tardo · 2007-11-14 18:46:13

ok lets make this easier: can you just archive the entire dir and post it somewhere? it's a lot easier that way.

lilsirecho · 2007-11-14 18:48:35

tardo;

Posted PKGBUILD and Patch in earlier post....

lilsirecho · 2007-11-14 19:05:10

Run PKGBUILD...

Halts at .... File to patch....

Directory now has ...PKG....SRC...

SRC has the patch included.

What procedure is required to makepkg with this PKGBUILD?

Cerebral · 2007-11-14 19:35:28

OMG stop bumping. People will help you out when they have the time - bumping constantly won't help.

The message "File to patch" means that the patch command can't find the _FILE_ you want to patch, not the patch itself.

tardo · 2007-11-14 19:59:17

Yea, for the record, the post above that contains the patch and pkgbuild is a PITA to read. I asked for the contents of the package so I could try to build the package myself and see which -Np# option you need.

If you're still reluctant, try changing the patch -Np# in the pkgbuild to 0 or 2 and see if that helps.

lilsirecho · 2007-11-14 21:00:43

Tardo;

I am not aware of what you requested since the data contained in the -svn is just the PKGBUILD and the PATCH as provided in my post.

I have decided to close this posting and skip the package altogether.

Arch Linux

#1 2007-11-12 00:34:16

PKGBUILD for unsermake has patch..not recognized

#2 2007-11-14 03:42:11

Re: PKGBUILD for unsermake has patch..not recognized

#3 2007-11-14 03:56:21

Re: PKGBUILD for unsermake has patch..not recognized

#4 2007-11-14 04:21:46

Re: PKGBUILD for unsermake has patch..not recognized

#5 2007-11-14 16:08:30

Re: PKGBUILD for unsermake has patch..not recognized

#6 2007-11-14 16:25:15

Re: PKGBUILD for unsermake has patch..not recognized

#7 2007-11-14 17:10:19

Re: PKGBUILD for unsermake has patch..not recognized

#8 2007-11-14 17:24:54

Re: PKGBUILD for unsermake has patch..not recognized

#9 2007-11-14 17:40:37

Re: PKGBUILD for unsermake has patch..not recognized

#10 2007-11-14 18:19:15

Re: PKGBUILD for unsermake has patch..not recognized

#11 2007-11-14 18:46:13

Re: PKGBUILD for unsermake has patch..not recognized

#12 2007-11-14 18:48:35

Re: PKGBUILD for unsermake has patch..not recognized

#13 2007-11-14 19:05:10

Re: PKGBUILD for unsermake has patch..not recognized

#14 2007-11-14 19:35:28

Re: PKGBUILD for unsermake has patch..not recognized

#15 2007-11-14 19:59:17

Re: PKGBUILD for unsermake has patch..not recognized

#16 2007-11-14 21:00:43

Re: PKGBUILD for unsermake has patch..not recognized

Board footer