Arch Linux User Repository

As SanskritFritz said, you can skip updating the tree by uncommenting _no_update="y". The PKGBUILD also asks you two times whether you want to continue, so it does offer a certain interactivity. Asking the user interactively whether he wants to update his or her tree would be a good idea though. I'm going to add it later this day.

@vl981 It does provide this functionality, but not interactively. Edit the PKGBUILD _no_update="y".

Hi. IMHO it would be great if this package could provide the same functionality as old kernel26zen-git provided, I mean here the ability to choose interactively either to update/not update source, just build/update and build.

I mark this out for date, because zen-stable-2.6.36-zen1 is in the snapshots. BTW, the git daemon is running again, I'm cloning the git repo right now.

IRC (#zen-sources @ Rizon) is probably the best news source.

This package is the best zen kernel package I've seen on AUR. I used kernel26zen-git so far, also thanks for taking that over and maintaining it. I'm going to try this as soon the zen server is healed. Where can I get the news about it?

The first time you run makepkg, the PKGBUILD will set up the build directory and then abort due to the missing kernel configuration. Then it is your task to navigate to the build directory (/src/build) and create one (by copying an existing one, running make menuconfig, gconfig, defconfig, whatever you want). Once set up there's no need to reconfigure it. The PKGBUILD will use that config whenever you try to build the package.

I suppose as long as everyone makes positively sure whatever they use keeps the tree so there is no unnecessary server load, who cares what is used or not. As long as we help the devs by protecting their servers so we don't kill them like has been happening. For me, what I've found the most helpful is to skip using yaourt or clyde with it and instead write a wrapper script to run makepkg -i on it, so I can also have the script also rebuild nvidia and other modules that I need. That way I can rebuild kernel and modules all in one shot and not have to think about having to rebuild modules when kernel is updated. I like to check over or tweak menuconfig whenever I build a new kernel. Haven't run the new pkgbuild yet, but just to check before I dig into modifying my wrapper for this, am I correct in seeing that the new pkgbuild no longer runs a menuconfig as part of the pkgbuild so I need to add a make menuconfig in my script just before the makepkg?

For some time yourt uses abs directory for it so no redownloading no reconfigurating ( for some pakage i neeed to change something to get abs working but for now it works on this package )

Exactly. Apart from that, on the very first run of makepkg the build process will abort due to the missing kernel configuration. Then the user has to set up his config and run makepkg again. I'm not sure whether that's possible with yaourt.