why don´t include the pkgbuild in the package

sabrewolf · 2006-04-21 22:02:35

so, you can see how the package was compiled, with an opsion like:

pacman -Qb foo.pgk.tar.bz2

b for build, is an example.

tomk · 2006-04-21 22:27:30

You can get the PKGBUILD from ABS or CVS.

Neuro · 2006-04-22 07:12:52

ABS is a bit of a overkill if you want to build just one package, and CVS isn't a conventional way of downloading PKGBUILDS + patches.

Is there any chance by which a script to download only the specified PKGBUILD be made? It'll be a better solution than including the PKGBUILD (and patches) in the package.

codemac · 2006-04-22 07:19:55

I've heard of this one website that lists all current / extra / unstable / testing packages on it's front page.

http://www.archlinux.org

I know it seems like I'm being an ass, but what more do you want? It's a front end to the cvs repos that all the pkgs are held in, and if you don't want to use cvsup and stay up to date with your ABS and only want one package, how will writing a binary speed up a process that you need net access for anyway?

There's a search box. If you want to build a specific package with it's PKGBUILD, go there.

Neuro · 2006-04-22 07:43:47

Now, there's no need to be sarcastic.

I know about the CVS web interface, and I use it. But downloading for example:
http://cvs.archlinux.org/cgi-bin/viewcv … ag=CURRENT
to a directory on your filesystem is a PITA, since you need to click-click all the things in the CVS tree.

Now, I'm not a CVS expert, and I don't know if this could be done. But a simple bash script or a binary that would download the whole CVS entry for a specified package with a simple "get-the-bloody-cvs-entry current/kernel26" would be much easier, wouldn't it?

sweiss · 2006-04-22 08:57:29

Have you tried looking at srcpac?

Neuro · 2006-04-22 08:57:59

Nevermind, I've found the solution here:
http://bbs.archlinux.org/viewtopic.php?p=158778#158778

sash · 2006-04-22 15:40:07

Neuro wrote:

Now, I'm not a CVS expert, and I don't know if this could be done. But a simple bash script or a binary that would download the whole CVS entry for a specified package with a simple "get-the-bloody-cvs-entry current/kernel26" would be much easier, wouldn't it?

This is very much possible, by using the cvs client. It could be as simple as

cvs co some_package_name

Maybe there is even a WIKI page on thins already. If not, it should be prety easy to put one up with the exact instructions.

soloport · 2006-04-22 16:53:34

Neuro wrote:

Nevermind, I've found the solution here:
http://bbs.archlinux.org/viewtopic.php?p=158778#158778

Glad it helped ;-) Here's an improvement...

Replace:

cvs -z3 co arch/build/kernels/kernel26

With:

cvs -z3 co -d kernel26 arch/build/kernels/kernel26

$ man cvs # reveals...

It is very convenient when checking out a single item to have the output
appear in a directory that doesn't contain empty intermediate directories.
In this case only, cvs tries to "shorten'' pathnames to avoid those empty
directories.

soloport · 2006-04-22 19:18:02

Neuro wrote:

Nevermind, I've found the solution here:
http://bbs.archlinux.org/viewtopic.php?p=158778#158778

Have posted some illustrative scripts, here.

Arch Linux

#1 2006-04-21 22:02:35

why don´t include the pkgbuild in the package

#2 2006-04-21 22:27:30

Re: why don´t include the pkgbuild in the package

#3 2006-04-22 07:12:52

Re: why don´t include the pkgbuild in the package

#4 2006-04-22 07:19:55

Re: why don´t include the pkgbuild in the package

#5 2006-04-22 07:43:47

Re: why don´t include the pkgbuild in the package

#6 2006-04-22 08:57:29

Re: why don´t include the pkgbuild in the package

#7 2006-04-22 08:57:59

Re: why don´t include the pkgbuild in the package

#8 2006-04-22 15:40:07

Re: why don´t include the pkgbuild in the package

#9 2006-04-22 16:53:34

Re: why don´t include the pkgbuild in the package

#10 2006-04-22 19:18:02

Re: why don´t include the pkgbuild in the package

Board footer