You are not logged in.
Makeworld is designed to build the entire repository, whereas this app rebuilds only the stuff on your system currently
Offline
what's actually the difference to makeworld?
makeworld - a makepkg wrapper to build multiple packages Usage: /usr/bin/makeworld [options] <destdir> <repo> [repo] ...
ok, it has AUR support, but AUr packages are compiled anyway....
am i missing smth?vlad
a full support..pacman and aur..and a beautiful output..for starter...and i think his going to work on it to improve
Last edited by aRcHaTe (2008-05-22 19:22:24)
Its a sick world we live in....
Offline
ok
thanks
vlad
Offline
I've edited the check_args() function to support 2 character arguments (ie: -X) for faster typing and removed the sysupgrade argument as it did the same thing as upgrade but wasn't included in the help, and edited the print_help() function to include the new shorter arguments, organised the output a bit nicer, and added two examples.
http://me.yarrt.com/print-help-check-args.txt
Not sure if you'll use it or not, but I thought I'd try to help
Offline
does no longer depends on yaourt, depends on rsync!
awesooome!!!!
Its a sick world we live in....
Offline
Question: If you recompile your entire system, then install a few things with pacman, is there a way to make the script just recompile those packages and not everything else again?
Offline
I've modified this to install packages you don't already have - as well as recompile them
Here is the installing function:
function install_packages()
{
if [ "$INSTALLING" == "TRUE" ]; then
echo "" > ${LOG_FILE_PACKAGES}
for EXTRA_FLAG in $INSTALLPKGS; do
if [ "`echo \"$EXTRA_FLAG\" | grep \"-\"`" == "" ]; then
echo ${EXTRA_FLAG} >> ${LOG_FILE_PACKAGES}
fi
done
build_multiple_packages
fi
}
The corresponding line in check_args():
--install) INSTALLING="TRUE"; INSTALLPKGS=$@ ;;
And the corresponding line in main():
install_packages
To test run it like this: pacbuilder --install package1 package2 package3 etc. It doesn't seem to work with packages in extra - but I am using the latest version of the script as a base.
Last edited by Barrucadu (2008-05-22 22:59:57)
Offline
Pretty sweet. Thanks a lot
Offline
Ah, you adopted my suggestion
Now all this script really needs is a --remove option, and it will be as good as a full-blown package manager. I'll have a look later at implementing one - if someone else hasn't made one by then.
Offline
@Cimi: I've had pretty good results so far. I did a --core rebuild, and the only real problems had to do with a few outdated PKGBUILDs. Of my 128 packages in core, I had about 12 of these that wouldn't rebuild, simply because the source package referred to in the PKGBUILD was not found. For 7 of these packages, I manually edited the PKGBUILD and rebuilt them not using pacbuilder. The remaining 5 packages I'm leaving as they are.
Now my problem is this: I've decided to try rebuilding another repository, but when I run the command './pacbuilder.sh --extra --verbose', it goes back to the 5 that were left over from the --core rebuild. I think the script is stuck.
I'm using r35 now; I had been using one of the earlier releases, when yaourt was still used. So the script should support --extra, I believe. At any rate, when I run --testing or --unstable, the script still insists on going back to those 5 unbuild packages from core.
Along these same lines, it would be good if I could tell pacbuilder that I want to leave some unbuilt packages as they are, an ignore package option, in other words. Maybe you've already got this and I missed it.
Thanks again. I think this has a lot of potential, as you can probably tell by the interest it's generated.
Last edited by dhave (2008-05-23 07:16:53)
Offline
@Cimi: I've had pretty good results so far. I did a --core rebuild, and the only real problems had to do with a few outdated PKGBUILDs. Of my 128 packages in core, I had about 12 of these that wouldn't rebuild, simply because the source package referred to in the PKGBUILD was not found. For 7 of these packages, I manually edited the PKGBUILD and rebuilt them not using pacbuilder. The remaining 5 packages I'm leaving as they are.
Now my problem is this: I've decided to try rebuilding another repository, but when I run the command './pacbuilder.sh --extra --verbose', it goes back to the 5 that were left over from the --core rebuild. I think the script is stuck.
I'm using r35 now; I had been using one of the earlier releases, when yaourt was still used. So the script should support --extra, I believe. At any rate, when I run --testing or --unstable, the script still insists on going back to those 5 unbuild packages from core.
Along these same lines, it would be good if I could tell pacbuilder that I want to leave some unbuilt packages as they are, an ignore package option, in other words. Maybe you've already got this and I missed it.
Thanks again. I think this has a lot of potential, as you can probably tell by the interest it's generated.
first of all, you can edit PKGBUILD by adding --edit!!!
Well, it should ask to resume or not, if you answer no then it shouldn't goes back using the 5 packages
Offline
another name suggestion: powerpill_pacman
Stand back, intruder, or i'll blast you out of space! I am Klixon and I don't want any dealings with you human lifeforms. I'm a cyborg!
Offline
Is there any way to reduce the timeout time for downloading packages? For what ever reason one of the sourceforge mirrors will not let me download, causing a ton of packages not to build. I know that reduce the time won't fix the package compiling but it waits like (5+ minutes) before going onto the next package
Offline
first of all, you can edit PKGBUILD by adding --edit!!!
O.K., that's a nice feature. Thanks.
Well, it should ask to resume or not, if you answer no then it shouldn't goes back using the 5 packages
I am dumber than a duck. I was inputing simply "n" instead of "no", even though the prompt clearly says "yes/no". When I input "no" instead of "n", the script responds correctly.
Sorry!
Offline
pyther:
If this problem is related to the use of "dl.sourceforge.net" instead of "downloads.sourceforge.net" you can simply add
sed -i -e "s/dl.sourceforge.net/downloads.sourceforge.net/" PKGBUILD
between "edit_pkgbuild" in line 242 and "get_pkginfo" in line 243, worked for me.
This is of course a temporary solution because it's not the job of a package management tool to fix the mistakes the packagers made
two - Arch64 | dwm | nvidia
three - Arch64 | dwm | nvidia
Offline
the dependency check&build should work muuuch better
please test it!
been waiting for this
great!
Its a sick world we live in....
Offline
Brilliant
Recompiling splashy with this resulted in not being able to run mkinitcpio without getting millions of errors. Recompiling splashy with the latest version made it all work
Offline
the output should be much better now when taking into account dependencies.
Also, I've fixed all the checks behind dependencies, so when it fails it will print what was wrong (missing dependency, makepkg error, general error...)
Last edited by Cimi (2008-05-24 12:12:50)
Offline
How about powerpac?
Last edited by roadboy (2008-05-24 12:34:32)
in /dev/null no one can hear your scream...
Turkish Archlinux & KDEmod Mirror Administrator
http://server.elsistech.com/archlinux/ ~ http://server.elsistech.com/archlinux/kdemod/
Offline