NumberOfConcurrentSearches
Set number of parallel search processes when running "pkgman --diffversions". Defaults to 5.
Don't set this value too high as it might significantly slow down the system with no further speed gain.
A value between 10 and 20 is pretty sane. Anyway, the number of possible parallel search processes is limited to 30.
* another new conf file variable : "MakepkgNiceLevel". Sets makepkg nice level when building packages. Not set by default. Can also be set with "-N|--nice" flag.
From the manpage:
-N, --nice <integer>
Run makepkg with given niceness value. Set this globally with MakepkgNiceLevel in pkgman.conf.MakepkgNiceLevel
Run makepkg with given niceness value when building packages. Not set by default.
Niceness levels can be integers from -20 to 19 depending on global settings (limits.conf). See "man nice".
* it is possible to choose which package to build with split PKGBUILDs.
* some output layout changes
As always, please read the manual page for more detailed information.
Vlad
PS: Though the manual page says so, it is not needed to rerun "pkgman --runmefirst" again (remained from r116).
]]>A new release r113 is out. I tested it for some weeks now and I would say it's stable.
* The most significant new feature is that pkgman now supports building split packages through makepkg.
From the man page:
If a PKGBUILD is split into multiple pkgname packages, then these are stored in the pkgbase backup directory. The pkgname directories are
symlinked to the pkgbase directory inside LocalPackages. Please do not remove these links.
These links are mainly needed for bash completion and for the --list, etc features.
If you already use pkgman and you update to r113, you need to rerun "pkgman --runmefirst".
* Another new feature is the "-t,--template" option. Useful to create a new PKGBUILD and use an existing one as a template.
From man page:
pkgman <packagename> --template <alt. packagename> [--pkgbuildversion <version>] [options]
This flag uses a given <alt. packagename> source tarball as a template for creating an own PKGBUILD.
With "-v,--pkgbuildversion" one can specify which version of a backed up <alt. packagename> source tarball to use.
Without "-v,--pkgbuildversion" the current <alt. packagename> sources are fetched from ABS or AUR - if available.
Eg:
pkgman kernel26-own -t kernel26 -rm
fetch kernel26 PKGBUILD, edit it, make a kernel26-own package and add it to local repository.
* Another new option:
--conf /path/to/alternate/conf/file
Specify another configuration file.
Useful if one wants to maintain multiple LocalPackages or LocalRepository directories.
For more information please read the man page.
PS: pkgman now relies on pacman's database (/var/lib/pacman/sync) to get the pkgbase of possibly split packages. So update it frequently to get accurate results - I assume most people do this anyway.
PPS: pkgman now uses ${XDG_CONFIG_HOME}/pkgman or $HOME/.config/pkgman - if first not set - as the default location for its conf files.
]]>syth tinyandbig > pkgman tinyandbig -ebs
==> NOTE: You can always leave by pressing Ctrl-c.
==> Choose a file you want to check or edit:
1 PKGBUILD
==> To copy a custom file press [a], to create
a new one press [c], press [s] to switch to
/root/pkgs/tinyandbig
to change the src or press [q] to quit.
==> ----------------------------------------------
==> q
==> [g]enerate integrity checksums?
==> ----------------------------------------------
==> n
==> Backing up files:
==> Do you also want to backup the source file?
==> [y]es or [else] to pass.
==> ----------------------------------------------
==> y
==> Making package: tinyandbig 0.1-1 x86_64 (Fri Apr 2 16:49:56 EDT 2010)
==> Retrieving Sources...
-> Downloading tinyandbiglinux64-0.1.tar.gz...
--2010-04-02 16:49:56-- http://tinyandbig.com/wp-content/uploads/tinyandbig/tinyandbiglinux64-0.1.tar.gz
Resolving tinyandbig.com... 81.169.131.121
Connecting to tinyandbig.com|81.169.131.121|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 132108347 (126M) [application/x-gzip]
Saving to: "tinyandbiglinux64-0.1.tar.gz.part"
100%[======================================>] 132,108,347 7.11M/s in 20s
2010-04-02 16:50:16 (6.35 MB/s) - "tinyandbiglinux64-0.1.tar.gz.part" saved [132108347/132108347]
==> Validating source files with md5sums...
tinyandbiglinux64-0.1.tar.gz ... Passed
==> Creating source package...
-> Adding PKGBUILD...
-> Adding tinyandbiglinux64-0.1.tar.gz...
-> Compressing source package...
==> Source package created: tinyandbig (Fri Apr 2 16:50:24 EDT 2010)
==> Do you want to tag the backed up src.tar.gz file?
==> Enter tag or hit [Return] to pass.
==> ----------------------------------------------
==>
==> Moving backed up sources to /root/pkgs/tinyandbig/.backup
==> Done!
==> ERROR: There are no tarballs available!
any ideas?
]]>PS: There is a new pkgman wiki at sf.net:
http://sourceforge.net/apps/mediawiki/p … =Main_Page
I don't have any problem now thank your detail reply.
]]>pkgman <metapackagename> -Mre
you can directly install them all with
pacman -Sy <metapackagename>
for example here is a metapackage for the last 2.6.29 kernel:
pkgname=meta-kernel26_working
pkgver=2.6.29.4_1
pkgrel=6
pkgdesc="kernel ${pkgver/_/-} metapackage with drivers (nvidia etc)"
arch=(x86_64)
license=('none')
groups=()
depends=('kernel26=2.6.29.4-1' 'kernel26-firmware=2.6.29-1' \
'nvidia-utils=180.51-1' 'nvidia=180.51-1' 'lib32-nvidia-utils=180.51-1')
source=()
md5sums=()
sha256sums=()build() {
echo
msg "Nothing to build . . ."
msg "This is only a metapackge!\n"
}# vim:set ts=2 sw=2 et:
so when you run
pkgman meta-kernel26_working -reM
all specified packages from the depends array are fetched either from the packagename backup directory (if available) or from http://arm.kh.nu/ and moved to the local repo.
vlad
]]>