October 2006 - Pacman-dev - lists.archlinux.org

[pacman-dev] $ARCH suffix on packages
by Aaron Griffin 11 Oct '06

11 Oct '06

So I actually expected someone to start this, as I was curious. I know frugalware uses the architecture suffix on packages, and Xentac thinks this is a good idea. I'd like to hear reasons. I don't really feel that "RPM and DEB do it" is a good enough reason. I mean, if that reason was good enough, we'd be using RPM/DEB in place of pacman packages. The way I see it, I don't think pacman needs to know the architecture it's running on. Installing "pkg-foo" should be no different on i686 or PPC. Therefore, I think that adding the architecture suffix is extra information that's not really needed. What is gained by having this suffix?

9 29

[pacman-dev] Documentation
by Aaron Griffin 09 Oct '06

09 Oct '06

I have merged all the changes from frugalware, and all pactests work (except for sync898 which VMiklos and I already talked about). Now, I'm on to the documentation. $ grep -ir "frugal" | grep -ve "@frugalware.com" | wc -l 385 That's without email addresses. So yeah, I didn't pay attention to the documentation patches. Most of these changes are PKGBUILD -> FrugalBuild. I think I caught all the pkg.tar.gz -> fpm and db.tar.gz -> fdb changes before patching. I'd like to see if we can some up with a decent way to allow for us to use the same documentation base, as sedding this stuff on merge seems like a waste of time. The simplest solution is to just make them all .in files and set autoconf variables like: BUILD_SCRIPT_NAME = PKGBUILD PKG_EXT = pkg.tar.gz #already discussed in the TODO etc etc Does this sound worthwhile? Are there other ideas? I'm trying to open up discussion here and look for any and all suggestions. Thanks in advance, Aaron

4 6

[pacman-dev] Problems with frugalware splitname changes
by Aaron Griffin 09 Oct '06

09 Oct '06

The changes to the alpm splitname function are fine and all, except they do not accomodate archlinux packages, which do not append the architecture to the end of the package name (instead we put them in directories based on the architecture). Could you please make these changes so that they can accomodate for either arch of frugalware? Currently, it directs pacman to install a foo-1.0-1-.pkg.tar.gz package. (note the trailing dash). I have a few more things to delve through, but I won't be back until late tonight, so I figured I could poke you guys to make the change (if you have time). Thanks, Aaron Griffin

6 21

[pacman-dev] [PATCH] Java bindings
by VMiklos 08 Oct '06

08 Oct '06

hi http://darcs.frugalware.org/darcsweb/darcsweb.cgi?r=pacman;a=commitdiff;h=2… so finally after python and perl, java bindings arrived :) udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

2 1

[pacman-dev] Time for changes
by Aaron Griffin 07 Oct '06

07 Oct '06

Ok, I think it's about time I picked up pacman developement, seeing as we really have no one else doing it. I've been busy, so I was really hoping someone else would volunteer, but what the hell. If you frugalware guys could send me a full diff (here or offlist) of your repo compared to the trunk, that'd be great. I don't like applying patches without verifying them, so I'm going to step through each hunk (this is why I originally requested them as the seperate patches sent to the ML, but I can deal with it either way). One thing i plan on doing right off the bat: I want to enable a side-by-side install with the current pacman, so that we can get some real testing by those (like me) who don't want to overwrite the stable pacman. This is just informational, but it shouldn't affect the frugalware guys. To the furgalware team: you have more experience with this new pacman that I do... could you give me a brief "what's changed" - functionality wise. I mean, when actually using pacman3, what is done differently? What future directions are we going for? I'd like to get this stable as soon as possible, but once that's done, I have a handful of nifty features I wanted to add (those on the dev list: I want to add filesystem hooks first, then some more advanced output logging). There are also some potential changes to gensync and friends, depending on what direction we go with some svn changes... but that's off topic. Anyway, let me know. Aaron Griffin - phrakture -

12 50