Xyne wrote:

...

...

3) Is there any way to avoid re-uploading a package when changing the PKGBUILD if the changes have no effect on the built package (e.g. appending packages to the depends array)?

Adding more depends does alter the package... But you can always alter the package in cvs and just do "cvs commit" for things that _really_ do not alter the package.

Allan

Thanks for the reply.

Will a cvs commit without a binary upload (e.g. when adding a package to the depends array) result in a new binary package in the repo with the correct information? Formulated another way, does the upload server create a new .PKGINFO file and replace the old one while keeping the installable package files?

The .PKGINFO file is created by makepkg and compressed inside the package. When you upload a package to the server, this file is extracted and an entry is made for the pacman database using this information. So any change that alters the .PKGINFO file or any installed files requires a new binary upload. Have a look at a PKGINFO file and note there are very few things that you can change without uploading a new package. Allan

On Sun, Apr 12, 2009 at 11:23:07PM +0200, Xyne wrote:

Allan McRae wrote:

...

The .PKGINFO file is created by makepkg and compressed inside the package. When you upload a package to the server, this file is extracted and an entry is made for the pacman database using this information. So any change that alters the .PKGINFO file or any installed files requires a new binary upload. Have a look at a PKGINFO file and note there are very few things that you can change without uploading a new package.

I know where the .PKGINFO is stored... I was just hoping that the server would be "smart" enough to handle changes that don't really require a package rebuild, e.g. extract .PKGINFO, update it, re-insert it. Uploading 600 MB * 2 in this case to change a package description just seems silly.

Who's mostly in charge of handling such things? Maybe I can help out a bit with some scripts or whatever (resumable uploads would also be good, for instance).

You could start by looking at devtools. The community repo will be using that system in the near future.