Package Builder

Hello
I created a package hierarchy with the package builder.
Now I want to hang out one package - not delete this package - only hangout it from the main package.
Is there realy no way or it's just me how is blind
Thanks for any help
Daniel

Hi Daniel Müller,
I think this thread may help you:
Re: Remove subpackage from package hierarchy
Regards,
Bruno Xavier.

Similar Messages

[svn] 3159: fix to target the correct player in the external library path for the packaged build file

Revision: 3159
Author: [email protected]
Date: 2008-09-09 12:53:37 -0700 (Tue, 09 Sep 2008)
Log Message:
fix to target the correct player in the external library path for the packaged build file
Modified Paths:
flex/sdk/trunk/frameworks/build_framework.xml

Hi Gaurang,
Were you able to resolve your issue?
Hope the following links help:
/message/7579461#7579461 [original link is broken]
Re: Required JAR files:
Regards,
Dao

Organizing package building wiki entries

Right now we have three separate wiki entries that describe the package building in Arch:
http://wiki.archlinux.org/index.php/Arc … _Standards
http://wiki.archlinux.org/index.php/The … guidelines
http://wiki.archlinux.org/index.php/ABS … _Explained
I started maintaining packages a few months ago, and while I was learning how to build packages I was getting a little tired of having to sift through multiple resources with duplicate information. This is kind of a shameless plug, but I took the entries, updated and re-wrote them:
http://www.bytetrap.com/blog/2008/09/16 … rch-linux/
Thoughts? Every factoid mentioned in those three wiki entries -should- be mentioned in my post. If I get enough thumbs up I'd be happy re-organize the current three wiki entries into the single entry that I compiled.

btartsa wrote:
I noticed in the "preparing the file'" section you recommend using pacman -Up (package file). What is the benefit of using the -p flag?
-p, --file
Signifies that the package supplied on the command line is a file and not an entry in the database. The file will be decompressed and queried. This is useful in combination with --info and --list.
I'm just wondering because I've never used it. Nice work!
I took that line pretty much verbatim from the wiki entry, but the -p flag I believe ensures that you install the package that you built instead of the pre-built binary from the pacman database. So this only really applies/comes in handy if you build a package from the PKGBUILD file when the binary already exists, preventing you from installing the binary.
Also, I don't think this is usually a big problem either because the package you build is usually named pkgname.tar.gz, while when you query a package via pacman, you just use the pkgname. So you usually just do pacman -U pkgname.tar.gz instead of pacman -U pkgname anyway. If for some reason your package file was named pkgname, you would have to use the -p flag to ensure that you install your pakcage instead of the pre-built binary.

[svn:fx-trunk] 11193: fix packaged build file for textlayout to accommodate the recent changes made to that project

Revision: 11193
Author:   [email protected]
Date:     2009-10-27 13:08:28 -0700 (Tue, 27 Oct 2009)
Log Message:
fix packaged build file for textlayout to accommodate the recent changes made to that project
QE notes: no
Doc notes:
Bugs: sdk-23302
Reviewer:
Tests run: checkintests
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-23302
Modified Paths:
    flex/sdk/trunk/frameworks/build_framework.xml

There are two main annoying problems with Flash Builder and swc's:
1. Flash Builder doesn't reflect changes made to swc files
Solution : First of all - keep your swc files inside your project folder, you can also disable global swc cache: change as3api.cpp code,refresh swc in flashBuilder bug!
2. Flash Builder breakes content inside swc files (and also popular problem "TypeError: Error #1034: Type Coercion failed: cannot convert flash.display::MovieClip@1f21adc1 to...")
Solution : locate the project .actionScriptProperties file and set useFlashSDK=”false” : Flash Builder 4.7 – useFlashSDK | In Flagrante Delicto!
In this case you can also download latest Apache Flex SDK to target new Flash player versions: http://flex.apache.org/
Hope this helps!
P.

OpenG Package Builder tool 0.1-alpha6 released

Hello Everyone,
There is a new version of the OpenG Package
Builder tool (ogrsc_package_builder package) available. This tool
allows you to create package files that can be installed using VI Package Manager.
This release resolves an issue caused by a LabVIEW 8.x bug with handling variant coercion (see here for bug details).
See here for more info about this release.
You can download and install this library (as well as all the OpenG libraries) using VI Package Manager.
Thank you,
Message Edited by Jim Kring on 03-04-2007 10:58 PM
Attachments:
package_builder.png ‏28 KB

Bob Y. wrote:
OK, but what is it and why should I use it? What need does it fulfill? I have been unable to find much documentation for this at the wiki page and maybe a couple of paragraphs here would help.
Thanks,
Bob Young
Hi Bob,
Yes, this info got burried. Basically, it's a tool for building LabVIEW-based software products. It is highly flexible/extensible and tries to fill the holes left by LabVIEW's built-in Application Builder. Here are some good links to more info:
OpenG Builder Homepage
OpenG Builder 1.0 Documentation
Thanks,
-Jim

OpenG Package Builder Release 0.1-alpha, Build packages for OpenG Commander

You can finally build Your own OpenG Commander packages (.ogp files) using the intuitive user interface of the OpenG Package Builder.
Read more about it, here.

Bob Y. wrote:
OK, but what is it and why should I use it? What need does it fulfill? I have been unable to find much documentation for this at the wiki page and maybe a couple of paragraphs here would help.
Thanks,
Bob Young
Hi Bob,
Yes, this info got burried. Basically, it's a tool for building LabVIEW-based software products. It is highly flexible/extensible and tries to fill the holes left by LabVIEW's built-in Application Builder. Here are some good links to more info:
OpenG Builder Homepage
OpenG Builder 1.0 Documentation
Thanks,
-Jim

Creative Cloud Packager - Build fail

Hi,
I am trying to build a package with CC 1.7 build 43 but receive the error 'Build fail'. I have pasted the log below. I have tried both x86 and x64 but it doesn't make a difference. I also tried building it without Illustrator but then received the same error with with Acrobat Pro.
The only adobe productso on my workstation is Reader and Flash, running Win7. Any ideas how i can fix this?
10/28/2014 09:41:28[INFO] AdobePackageBuilder - Build Version - 1.7.0.43
10/28/2014 09:41:28[INFO] AdobePackageBuilder - Logging Level verbosity Set to 4
10/28/2014 09:41:58 [INFO] AdobePackageBuilder - Successfully retrieved TargetName from OptionXML.
10/28/2014 09:42:15 [INFO] AdobePackageBuilder - Sucessfully extracted the product at C:\Users\brettm\AppData\Local\Temp\{EE9A7B5D-B687-482F-906D-3BC2C4C17DAA}\ACCCx2_8_1_451
10/28/2014 09:42:15 [INFO] AdobePackageBuilder - Extraction completed with return code = 0
10/28/2014 09:42:51 [WARN] AdobePackageBuilder - No file exist at (C:\CC\QLS_Digital\x86\QLS_Digital_x86\Build\ASU\Tools\CCC\Uninstall\deploy\remove.xml)
10/28/2014 09:42:55 [INFO] AdobePackageBuilder - Copied File (payloads\Media_db.db)
10/28/2014 09:42:55 [INFO] AdobePackageBuilder - Copied File (payloads\Media_db.sig)
10/28/2014 09:42:55 [INFO] AdobePackageBuilder - Copied File (payloads\Setup.xml)
10/28/2014 09:42:55 [INFO] AdobePackageBuilder - ASU at Path (C:\CC\QLS_Digital\x86\QLS_Digital_x86\Build\Setup\APRO11.0.0en_GB\Set-up.exe) is not found. Skipping copying and renaming.
10/28/2014 09:44:23 [INFO] AdobePackageBuilder - Copied Setup file/folder (packages)
10/28/2014 09:44:27 [INFO] AdobePackageBuilder - Copied Setup file/folder (resources)
10/28/2014 09:44:27 [INFO] AdobePackageBuilder - Copied File (Set-up.exe)
10/28/2014 09:44:28 [INFO] AdobePackageBuilder - Copied File (payloads\Media_db.db)
10/28/2014 09:44:28 [INFO] AdobePackageBuilder - Copied File (payloads\Media_db.sig)
10/28/2014 09:44:28 [INFO] AdobePackageBuilder - Copied File (payloads\Setup.xml)
10/28/2014 09:45:08 [INFO] AdobePackageBuilder - Copied Setup file/folder (packages)
10/28/2014 09:45:11 [INFO] AdobePackageBuilder - Copied Setup file/folder (resources)
10/28/2014 09:45:11 [INFO] AdobePackageBuilder - Copied File (Set-up.exe)
10/28/2014 09:45:12 [INFO] AdobePackageBuilder - Copied File (payloads\Media_db.db)
10/28/2014 09:45:12 [INFO] AdobePackageBuilder - Copied File (payloads\Media_db.sig)
10/28/2014 09:45:12 [INFO] AdobePackageBuilder - Copied File (payloads\setup.xml)
10/28/2014 09:46:09 [ERROR] AdobePackageBuilder - Failed to unzip the file (payloads\AdobeIllustrator18-mul-300914132703\Assets1_1.zip) from the zip file (C:\Users\brettm\AppData\Local\Adobe\AAMUpdater\1.0\Install\AdobeIllustrator18-mul\18.1.0 .430.2\setup.zip).
10/28/2014 09:46:09 [ERROR] AdobePackageBuilder - Failed to unzip the update - C:\Users\brettm\AppData\Local\Adobe\AAMUpdater\1.0\Install\AdobeIllustrator18-mul\18.1.0. 430.2\setup.zip.
Regards,
Brett.

If I recall correctly I got around this by deleting everything under the C:\Users\brettm\AppData\Local\Adobe\AAMUpdater\1.0\Install directory and whitelisted the following address in our proxy server. Then I started all over again and it worked. It always failed towards the end of the build so I can only assume it was doing some final checks with Adobe servers to make sure I had the proper licencing or something like that. Hope this helps.
ccmdl.adobe.com:80
swupmf.adobe.com:80
swupdl.adobe.com:80
https://na1mbls.licenses.adobe.com
https://ims-na1.adobelogin.com
https://adobeid-na1.services.adobe.com
https://na1r.services.adobe.com
http://activate.adobe.com
https://activate.adobe.com
http://adobe.activate.com
https://adobe.activate.com
ccmdls.adobe.com:443
ims-na1.adobelogin.com:443
na1r.services.adobe.com:443
prod-rel-ffc-ccm.oobesaas.adobe.com:443
lm.licenses.adobe.com:443
www-du1.adobe.com
Regards,
Brett.

[SOLVED] 'wordgrinder' package build fails

I'm trying to build a package out of this program here: http://aur.archlinux.org/packages.php?ID=17015
I download the tarball, extract it into my builds directory, enter the wordgrinder directory and enter 'makepkg -s'. I've only done this sort of thing once or twice but it worked then. This time, however, it ends with a build error:
(... lots of patching lines...)
pm: bootstrapping...
modemuncher.h:4: warning: cast from pointer to integer of different size
pm: creating new intermediate file cache in '.pm-cache'
gcc "-Wall" "-Os" "-I/usr/include/ncursesw" "-I/usr/include/lua" "-D_XOPEN_SOURCE_EXTENDED" "-D_XOPEN_SOURCE" "-DVERSION=\"0.2\"" "-DFILEFORMAT=2" "-DPREFIX=\"/usr\"" "-DNDEBUG" -c -o ".pm-cache/1-utils.o" "src/c/utils.c"
src/c/utils.c: In function 'readu8_cb':
src/c/utils.c:93: warning: implicit declaration of function 'lua_tointeger'
src/c/utils.c: In function 'writeu8_cb':
src/c/utils.c:107: warning: implicit declaration of function 'luaL_checkinteger'
src/c/utils.c: In function 'utils_init':
src/c/utils.c:168: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'funcs'
src/c/utils.c:168: error: 'funcs' undeclared (first use in this function)
src/c/utils.c:168: error: (Each undeclared identifier is reported only once
src/c/utils.c:168: error: for each function it appears in.)
src/c/utils.c:168: error: expected expression before ']' token
src/c/utils.c:177: warning: implicit declaration of function 'luaL_register'
rm -f ".pm-cache/1-utils.o"
pm: object 'cfile', defined at pmfile:71, failed to build with return code 256
==> ERROR: Build Failed.
Aborting...
Can anybody tell me what's going wrong?
Last edited by chochem (2008-08-19 09:40:39)

Garns wrote:
chochem wrote:BTW I was beta-testing the new version (0.3) while I was on Ubuntu and it looks quite impressive. Some neat new features, such as being able to navigate the document by headline-structure, easy moving text in between documents - introducing the Scrapbook - and possibly even... wait for it... undo (no promises, though). Sadly it says orphaned in AUR so Iguess it might be a while before it's available on Arch...
I adopted it . I'll update it to 0.3 as soon as there is a release. As orphaned packages in AUR are free for anyone to adopt, you could have done this as well.
Cool, thanks Yes, well but ... seeing as today is Day Two of my entire Arch experience, I figured I'd wait a bit before inflicting my workmanship on others. Funny thing is, I found out, I'm already contributing unwittingly: Searching AUR for MPD stuff, I found that somebody had posted a link to some old bash script hacks I've done

HI I am having the following error message in Package Builder please help?

Wed Jun 19 08:23:11 2013
[INFO] AdobePackageBuilder - Build Version - 1.0.0.54
Wed Jun 19 08:23:11 2013
[INFO] AdobePackageBuilder - Logging Level verbosity Set to 4
Wed Jun 19 08:23:12 2013
[INFO] AdobePackageBuilder - START utilCopySrcFolderToDstFolder /Applications/Utilities/Adobe Application Manager/CCP/toolkit/../toolkit/PackageTemplate/CS6/Template_Uninstall.bin /Volumes/STORAGE/FOM EDITORS/Build/FOM EDITORS_Uninstall.pkg
Wed Jun 19 08:23:12 2013
[INFO] AdobePackageBuilder - START utilCopySrcFolderToDstFolder /Applications/Utilities/Adobe Application Manager/CCP/toolkit/../toolkit/PackageTemplate/CS6/Template_Install.bin /Volumes/STORAGE/FOM EDITORS/Build/FOM EDITORS_Install.pkg
Wed Jun 19 08:23:12 2013
[INFO] AdobePackageBuilder - START utilCopySrcFolderToDstFolder /Applications/Utilities/Adobe Application Manager/CCP/toolkit/../utilities/APTEE/CS6 /Volumes/STORAGE/FOM EDITORS/Build/FOM EDITORS_Install.pkg/Contents/Resources/ProvisioningTool
Wed Jun 19 08:23:12 2013
[INFO] AdobePackageBuilder - START utilCopySrcFolderToDstFolder /Applications/Utilities/Adobe Application Manager/CCP/toolkit/../utilities/APTEE/CS6 /Volumes/STORAGE/FOM EDITORS/Build/FOM EDITORS_Uninstall.pkg/Contents/Resources/ProvisioningTool
Wed Jun 19 08:23:15 2013
[ERROR] AdobePackageBuilder - There is no packages folder inside (/tmp/C7BDF4E6-9B7E-4B33-B025-81089FD1186A/ACCCx181). ASU is InValid
Wed Jun 19 08:23:15 2013
[ERROR] AdobePackageBuilder - Unable to extract/Mount AAM ASU (/Users/ladmin/Library/Application Support/Adobe/CCP//AdobeCCPCache/AAM/AdobeSetupUtility/ACCCx181.dmg)

I had the same problem as well. It was resolved with the release of CC Packager 1.1
http://blogs.adobe.com/oobe/2013/06/creative-cloud-packager-1-1-a-big-week-for-cc-team-ent erprise-customers.html
However, Im having a problem along with other people with the Photoshop CC and InDesign CC packages that are created when you attempt to install them

[SOLVED] How to patch package build (uzbl-git)

Hello,
I am experiencing a similar issue while building uzbl-git as reported here in the last few posts https://aur.archlinux.org/packages.php? … 2&detail=1
When running "makepkg -s", I receive the following error:
creating /usr/lib/python3.2/site-packages/uzbl
error: could not create '/usr/lib/python3.2/site-packages/uzbl': Permission denied
make: *** [install-event-manager] Error 1
A user on the page posted a patch for this issue:
PKGBUILD diff:
======
14,15c14,15
< source=()
< md5sums=()
> source=('Makefile.patch')
> md5sums=('1fb21dc7128e11d9a91351702c5fee53')
45a46,48
>
> # fix python site-packages installation
> patch -p0 < "$srcdir/Makefile.patch"
=====
Makefile.patch:
=====
--- Makefile 2012-06-26 15:00:00.017779376 +0000
+++ Makefile.fixed 2012-06-26 14:54:24.969594488 +0000
@@ -12,6 +12,7 @@
PYTHON=python3
PYTHONV=$(shell $(PYTHON) --version | sed -n /[0-9].[0-9]/p)
COVERAGE=$(shell which coverage)
+PYINSTALL_EXTRA=--prefix="${DESTDIR}${PREFIX}"
# --- configuration ends here ---
=====
Could someone enlighten me on how this patch should be applied? I have looked over the patching page on the arch wiki, but am still not sure. Should those lines be added at lines 14,15 and 45,46,48 in the PKGBUILD, respectively, and should I then create the file makefile.patch in the same directory with the second part of the code? It is unclear to me as both source=() and md5sums=() are not anywhere in the PKGBUILD, so I can't remove these lines as the patch suggests if I am reading it correctly (I have no coding experience).
Someone posted an alternative patch, I am note sure if this is any easier to apply (https://github.com/keis/uzbl/commit/d4c … 6874dda0ea)
Thank you in advance.
Last edited by OLSHoya (2012-09-11 19:51:24)

PKGBUILD
# Maintainer: Mark Foxwell <[email protected]>
# Contributor: Dieter Plaetinck <[email protected]>
# Contributer: Brendan Taylor <[email protected]>
# Contributer: L42y <[email protected]>
pkgname=uzbl-git
pkgver=20120212
pkgrel=1
pkgdesc="All uzbl web interface tools: latest from the git master branch"
arch=('i686' 'x86_64')
url="http://github.com/Dieterbe/uzbl/"
license=('GPL3')
depends=('libwebkit3' 'socat' 'zenity' 'xclip' 'dmenu' 'python2' 'pygtk')
makedepends=('git' 'pkgconfig' 'libwebkit>=1.2.0')
source=('Makefile.patch')
md5sums=('1fb21dc7128e11d9a91351702c5fee53')
provides=('uzbl-core' 'uzbl-browser' 'uzbl-tabbed')
conflicts=('uzbl-core' 'uzbl-browser' 'uzbl-tabbed' 'uzbl-experimental-git')
_gitroot="git://github.com/Dieterbe/uzbl.git"
_gitname="uzbl"
build() {
cd "$srcdir"
msg "Connecting to GIT server...."
if [ -d $_gitname ] ; then
cd $_gitname && git pull origin
msg "The local files are updated."
else
git clone $_gitroot $_gitname
fi
msg "GIT checkout done or server timeout"
msg "Starting make..."
rm -rf "$srcdir/$_gitname-build"
git clone "$srcdir/$_gitname" "$srcdir/$_gitname-build"
cd "$srcdir/$_gitname-build"
patch -p0 < "$srcdir/Makefile.patch"
for file in bin/*; do
sed -i 's_#!/usr/bin/env python$_#!/usr/bin/env python2_' $file
done
sed -i -e "s|#![ ]*/usr/bin/python$|#!/usr/bin/python2|" \
-e "s|#![ ]*/usr/bin/env python$|#!/usr/bin/env python2|" \
$(find ./ -name '*.py')
make
package(){
cd "$srcdir/$_gitname-build"
make DESTDIR="$pkgdir" PREFIX=/usr install
Makefile.patch
--- Makefile 2012-06-26 15:00:00.017779376 +0000
+++ Makefile.fixed 2012-06-26 14:54:24.969594488 +0000
@@ -12,6 +12,7 @@
PYTHON=python3
PYTHONV=$(shell $(PYTHON) --version | sed -n /[0-9].[0-9]/p)
COVERAGE=$(shell which coverage)
+PYINSTALL_EXTRA=--prefix="${DESTDIR}${PREFIX}"
Save them both in the same folder and run makepkg. After you save Makefile.patch run "md5sum Makefile.patch" and update the md5sums array in the PKGBUILD if you need to.

Package build error [SOLVED]

Hi there.
I am trying to build a pkg (nitrogen) from AUR using ABS. All the dependancies are installed, however i get an error from the configure script.
the makepkg output is :
==> Making package: nitrogen 1.0_rc2-1 (Thu May 18 12:56:43 UTC 2006)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
==> Using local copy of nitrogen-1.0-rc2.tar.gz
==> Validating source files with MD5sums
nitrogen-1.0-rc2.tar.gz ... Passed
==> Extracting Sources...
==> tar --use-compress-program=gzip -xf nitrogen-1.0-rc2.tar.gz
==> Removing existing pkg/ directory...
==> Starting build()...
checking whether to enable maintainer-specific portions of Makefiles... no
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... ccache gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether ccache gcc accepts -g... yes
checking for ccache gcc option to accept ANSI C... none needed
checking dependency style of ccache gcc... gcc3
checking for library containing strerror... none required
checking how to run the C preprocessor... ccache cpp
checking for egrep... grep -E
checking for ANSI C header files... yes
./configure: line 3450: ++: command not found
checking whether we are using the GNU C++ compiler... yes
checking whether ccache g++ accepts -g... yes
checking dependency style of ccache g++... gcc3
checking for ranlib... ranlib
checking for a BSD-compatible install... /bin/install -c
checking how to run the C++ preprocessor... ccache g++ -E
checking for ANSI C header files... (cached) yes
checking for pkg-config... /usr/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GLIB2... configure: error: Package requirements (glib-2.0 >= 2.6.0) were not met:
No package 'glib-2.0' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables GLIB2_CFLAGS
and GLIB2_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
make: *** No targets specified and no makefile found. Stop.
==> ERROR: Build Failed. Aborting...
glib2 is also installed on the system.
Any ideas why this happens?
Thanks in advance.

Ok i solved it. I had to install pkg-config in /usr and not in the default /usr/local

Repository package building script

I've been using a script to build all the packages for my repo for some time, but it was pretty hacked together, so I decided to rewrite it today. I made it so that it works with both makepkg and versionpkg. The assumption is that you make a directory with this script and two directories (make and version). The "make" directory contains directories with only "makepkg" packages, and "version" contains directories with "versionpkg" packages. You execute the script in the top directory, an it will recurse though "make" and "version" and build all the packages to a single location.
It Works for Me! (tm)
An example building directory structure:
buildall.sh
builtlog.log
make
- any2dvd
- gimp-devel
- gmrun
version
- xfwm4-svn
- xfmedia-svn
- gaim-cvs
Script:
#!/bin/bash
REPO_PACKAGES=/path/to/built/packages
REPO_ARCHIVES=/path/to/archive
LOGFILE=builtlog.log #change this to whatever you want the logfile to be called
############ DO NOT EDIT BELOW THIS LINE! ###################
TOP_DIR=`pwd`
if [ -e "$LOGFILE" ]; then
echo "Previous log found, saving as ${LOGFILE}.old"
mv ${LOGFILE} ${LOGFILE}.old
fi
echo "Creating new log: ${LOGFILE}"
touch ${LOGFILE}
if [ ! -d "$REPO_ARCHIVES" ]; then
mkdir ${REPO_ARCHIVES}
fi
for i in `ls`; do
if [ -d "$i" ]; then
BUILD_COMMAND=`basename "$i"`pkg
HOLDING_DIR=`pwd`
cd $i
for p in `ls`; do
if [ -d "$p" ]; then
cd $p
START_TIME=`date +%Y %m-%d (%H:%M)`
echo " "
echo -e "33[0;36m ${START_TIME}:33[0m Starting build of ${p}..."
${BUILD_COMMAND} -w ${REPO_PACKAGES} >/dev/null 2>&1
if [ $? -eq 0 ]; then
END_TIME=`date +%Y %m-%d (%H:%M)`
echo -e "33[0;36m ${END_TIME}:33[1;32m ${p} built sucessfully."
echo "$p built sucessfully on ${END_TIME}" >>${TOP_DIR}/${LOGFILE}
else
END_TIME=`date +%Y %m-%d (%H:%M)`
echo -e "33[0;36m ${END_TIME}:33[1;31m failed."
echo "$p failed to build." >>${TOP_DIR}/${LOGFILE}
fi
#Move all but latest package to $REPO_ARCHIVE
mv `ls ${REPO_PACKAGES}/${p}*| sed '$d'` ${REPO_ARCHIVES} >/dev/null 2>&1
cd .. #Go back to parent directory
else
/bin/true
fi
done
cd ${HOLDING_DIR} #Start with the next batch
else
/bin/true
fi
done
cd ${TOP_DIR}
echo " "
echo -e "33[1;31m -------- Failed Packages: --------- 33[0m"
fgrep "failed" ${LOGFILE}
if [ $? -eq 1 ]; then
echo -e "33[1;32m No packages failed to build.33[0m"
fi
echo " "
echo "Check ${LOGFILE} for details."
exit 0

I have a script I will be releasing in the next 24 hours that should do this for you - working from Bridge. It will still initially be at the test stage but it should work and if it doesn't I will help you to make it work. If you are interested send me an email andrew at ps-scripts.com
Andrew

Solaris packaging - "build" class action script

I tried to create a package with a build class action script but having problem with it. I am wondering if any one could give me hint on how to solve this problem? I tried to follow the example on the Solaris tutorial but it didn't work either.
In the prototype file, I have added: e build /etc/randomtable=etc/randomtable ? ? ?
In the pkginfo I have added: CLASSES=�none build�
Content of etc/randomtable in my build directory:
!install
# randomtable builder
if [ -f $PKG_INSTALL_ROOT/etc/randomtable ]; then
echo "/etc/randomtable is already in place.";
else
echo "# /etc/randomtable" > /etc/randomtable
echo "1121554 # first random number" >> /etc/randomtable
fi
!remove
# randomtable deconstructor
if [ -f $PKG_INSTALL_ROOT/etc/randomtable ]; then
# the file can be removed if it's unchanged
if [ egrep "first random number" /etc/randomtable ]; then
rm /etc/randomtable;
fi
fi
The error I got after running pkgadd on that package:
Modifying /etc/randomtable
/var/sadm/pkg/BPCttdb.2/save/build/etc/randomtable: !install: not found
/var/sadm/pkg/BPCttdb.2/save/build/etc/randomtable: !remove: not found
/var/sadm/pkg/BPCttdb.2/save/build/etc/randomtable: test: unknown operator first random number
pkgadd: ERROR: class action script did not complete successfully
Some links related to class action script for solaris build:
http://docs.sun.com/app/docs/doc/817-0406/6mg76stf7?a=view
http://dlc.sun.com/osol/docs/content/PACKINSTALL/ch5pkgcasestudies-80583.html#ch5pkgcasestudies-56
Thanks!

I looked at the build script (/usr/sadm/install/scripts/i.build and r.build), and didn't see anything that parses the "!" directive. I'm not very familiar with build scripts, and the documentation is actually inherited from the original SVR4 documentation (not originating from Sun). But in looking at an example of a script that uses the build class, it expects the first argument to be either "install" or "remove" when called. So your example would look like this below. Note that my comment about the escaped comment can be ignored. It's surrounded by quotes, so is okay.
if [ $1 = install ] ; then
# randomtable builder
if [ -f $PKG_INSTALL_ROOT/etc/randomtable ]; then
echo "/etc/randomtable is already in place.";
else
echo "# /etc/randomtable" > /etc/randomtable
echo "1121554 # first random number" >> /etc/randomtable
fi
else
# randomtable deconstructor
if [ -f $PKG_INSTALL_ROOT/etc/randomtable ]; then
# the file can be removed if it's unchanged
if \[ egrep "first random number" $PKG_INSTALL_ROOT/etc/randomtable \]; then
rm /etc/randomtable;
fi
fi
So basically the SVR4 Applications Developers Guide incorrectly tries to use the "!install" and "!remove" commands.
-- Alan
Edited by: alanst on Apr 4, 2008 12:26 PM

Where can I find old package builds and associated files?

In particular I need to set up and test a PHP 5.2.17 server so that I can run some tests on a website in order to debug it enough to get it running on a php 5.3.x webserver.
So what I am looking for is the PKGBUILD and patch files for php 5.2.17.

Go to the packages page http://www.archlinux.org/packages/extra/i686/php/ and on the top righthand side you have a box labeled 'Package Actions' - lot's of useful stuff there, including 'Source Files'. Use the 'Log' tag to go back in time.
http://projects.archlinux.org/svntogit/ … e05a4d66fe is 5.2.10, next is version 5.3.
http://projects.archlinux.org/svntogit/ … e05a4d66fe
Last edited by karol (2011-09-14 11:07:25)

A64 optimization package building?

Well, I Have started to mess with A64 flags in the makepkg.conf file. For my first compile I decided to use Red_over_Blue's aterm example. Since this was my first attempt at a package I just wanted to see if it worked properly. So I did the pacman -A aterm-0.4.2-4.pkg.tar.gz
It worked flawlessly, but, it left me with a few questions.
Since I am compiling for A64 style cpu why when I pacman it and then run the aterm it worked without issues? Arch by default and my system is i686 currently. The package I built should be A64 only shouldn't it?
Here is my makepkg.conf settings that I used.
export CARCH="k8"
export CHOST="k8-pc-linux-gnu"
export CFLAGS="-march=k8 -02 -pipe"
export CXXFLAGS="-march=k8 -02 -pipe"
I am not sure if I was supposed to change the CARCH and CHOST options. I looked at the options they were using on gentoo and found -march=k8 is the default for A64 style cpu's.
So the question is, is my package true A64? Or is it just optimized but for 32bit? If I missed something here what do I do for a true A64 setup?
Any input is good input thanks for any replies.

you have no issues with it, because your cpu supports i686 and k8
if e.g. i would try your pkg, it would not work at all --- because my cpu do not support the commands the binary will give to it
if you only made one pkg, then your system is mostly running i686 and only this pkg is possible to run k8 --- what you need to do is a makeworld of all pkgs you want ... this can give big trouble, because of e.g. gcc and others
good luck

Package Builder

Similar Messages

Maybe you are looking for