You are not logged in.
With srcpac 0.3 (it really was time to release), srcpac -h outputs the usual usage information and the added srcpac options. No man page needed
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
However, srcpac -Sh gives:
usage: pacman {-S --sync} [options] [package]
options:
-c, --clean remove old packages from cache directory (use -cc for all)
-d, --nodeps skip dependency checks
-f, --force force install, overwrite conflicting files
-g, --groups view all members of a package group
-i, --info view package information
-l, --list list all packages belonging to the specified repository
-p, --print-uris print out download URIs for each package to be installed
-s, --search search remote repositories for matching strings
-u, --sysupgrade upgrade all packages that are out of date
-w, --downloadonly download packages but do not install/upgrade anything
-y, --refresh download fresh package databases from the server
--ignore <pkg> ignore a package upgrade (can be used more than once)
--config <path> set an alternate configuration file
--noconfirm do not ask for any confirmation
-v, --verbose be verbose
-r, --root <path> set an alternate installation root
-b, --dbpath <path> set an alternate database location
which is a little confusing regarding the -b option.
Offline
Looks like Judd added an option that directly conflicts with srcpac. I thought -b was a good one for build. I guess I'll have to change that one day.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
I added a manpage, added --ignore support, and fixed a conf handling bug.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
8)
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
Ya know, I've still yet to use srcpac... maybe I'll try that tonight
Offline
ok, dredging up an old thread, but didn't want to start a new srcpac thread.
Once abs is able to hit the AUR, srcpac is going to be invaluable!
One thing though, as I've just begun messing with srcpac - if I use srcpac exclusively, and let's say I setup some configure options for vim in srcpac.conf - when vim7 is released, will "srcpac -Syu" catch it, understand it was compiled from source, and recompile?
If this isn't the case, it'd be a nice feature...
Anyway, crossing my fingers until I can cvsup the AUR repo...
Offline
To respond a while after these things were posted:
re: USE flags
srcpac uses sed commands to replace chunks of the PKGBUILD. This is really a poor man's USE flags.
re: does srcpac remember which packages were from source
yes, it will. Check out the output of srcpac -Qi <some package you built>.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
How would I uncomment a line in a PKGBUILD using srcpac? I want to uncomment the following lines from the subversion PKGBUILD and place the entry into srcpac.conf:
# make DESTDIR=$startdir/pkg javahl
# make DESTDIR=$startdir/pkg install-javahl
The tricky part is that the delimiter for srcpac.conf is the # that I wish to uncomment.
Thanks!
Darin
Offline
You don't have to use # as the substitute delimiter. You can use / or % or anything you'd like.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
Hmmm... it didn't seem to work. I added the following into my srcpac.conf
conf_subversion=('%# make DESTDIR=$startdir/pkg javahl%make DESTDIR=$startdir/pkg javahl%' '%# make DESTDIR=$startdir/pkg install-javahl%make DESTDIR=$startdir/pkg install-javahl%')
It built without error, but the javahl library is not installed. When I uncomment the lines by hand and build the package, everything works fine. I'd just like to automate it with srcpac.
Offline
You have to be aware of the $. $ means end-of-line in regexp speak.
Also, check out the -o option for srcpac. It lets you inspect the PKGBUILD after changes have been applied without building the package.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
Ah, yes. Thank you. I also noticed that the -o option actually changes the PKGBUILD, so if it takes a little bit of experimenting to get it correct one may have to update the PKGBUILD from cvs to get it back to its original condition. Here is a patch to srcpac that sends the output to stout without ever modifying the PKGBUILD.
Thanks for srcpac and the help!
Darin
--- srcpac 2005-09-13 21:10:23.000000000 +0000
+++ srcpac.patched 2005-09-13 21:10:23.000000000 +0000
@@ -72,6 +72,19 @@
fi
}
+output_confs()
+{
+ varname=`echo $1 | sed 's#-#X#g'`
+ eval num_conf=${#conf_$varname[@]}
+ if [ $num_conf -gt 0 ]; then
+ sedvar=""
+ eval "for (( j = 0 ; j < $num_conf ; j++ )); do
+ sedvar="${sedvar}s${conf_$varname[$j]};"
+ done"
+ eval sed "$sedvar" $2/PKGBUILD
+ fi
+}
+
build_packages()
{
action="build"
@@ -426,8 +439,7 @@
for pkgdir in $candidates; do
if [ -f $pkgdir/PKGBUILD ]; then
# Look for config options and apply them
- do_confs $i $pkgdir
- less $pkgdir/PKGBUILD
+ output_confs $i $pkgdir | less
success=1
break
fi
Offline
Hmmm, submit that to the bug tracker. I may use that.
What I normally do is srcpac -Syo, the -y always updates from cvs first. That way you know it's right no matter what.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
I inlined the patch, and then saw I could attach it after the task was created, so it is in both places.
Thanks again --
Darin
Offline
Hi.
I just want to know how can I use CFLAGS in srcpac? Doesn't it takes this flags from makepkg.conf???
I'm trying to update the whole system using srcpac -Syb, but while installing the firest built package it tells me that some files are existing in my filesystem. The --force option seems not to work in srcpac, so I can't update my system automatically.
Sorry for your support. Arch is great distro, I like it very much
Sorry for my english
Offline
I really like the idea of srcpac. Is this project discontinued ?
Offline
Nope, srcpac is still valid, and it still works fine. It's not discontinued, just idle. pacman -S srcpac
Offline
Nope, srcpac is still valid, and it still works fine. It's not discontinued, just idle. pacman -S srcpac
There are several rather old requests here:
http://bugs.archlinux.org/index.php?tas … ing=srcpac
When will we see a new release ?
Offline
If i try to install anything using srcpac, i just get a
Error: failed to build "pidgin"
It gives me that for anything I try to install. Any ideas on what the issue is?
Offline
Does this program still work?
Offline
I hope so, I am trying to resuscitate this project.
Please report any bug, thanks!
Offline
...and here we are! srcpac 0.8 is out
Offline
Hello, I just found this whilst searching for source building options.
Has anyone used srcpac and mkarchroot together? Is there a way to make mkarchroot use srcpac in place of pacman and can I set it up so it compiles everything for i586?
I'd like to build a small server to run on some old kit. This looks promising...
Offline