Roman Kyrylych wrote:

There is a script for coloured pacman output somewhere on BBS. You can also include one of repo/cache cleanup scripts (based on filename matches) that available on ML and BBS. (and adding to git would be nice)

The coloured pacman output appears to be a patched version of the pacman frontend, not a script. http://bbs.archlinux.org/viewtopic.php?id=29624 http://aur.archlinux.org/packages.php?ID=11827 The cache clean-up script that I found is: http://bbs.archlinux.org/viewtopic.php?pid=330422#p330422 The script does not seem ready (with the big warning at the top and all...) so I am against including it at the moment. I'll wait and see if that functionality makes it into pacman and if not then consider including it when its ready. Allan

Allan McRae wrote:

The cache clean-up script that I found is: http://bbs.archlinux.org/viewtopic.php?pid=330422#p330422 The script does not seem ready (with the big warning at the top and all...) so I am against including it at the moment. I'll wait and see if that functionality makes it into pacman and if not then consider including it when its ready.

Anyway, that one is less interesting because it doesn't really work on filenames, it uses the -Si pacman output.

Allan McRae wrote:

Hi everyone,

With the release of pacman 3.1.2 I was reminded to get around to putting a pacman-contrib package into AUR/community like I said I would [1]. I have categorized the files in the contrib directory below.

Utilities: pacdiff pacsearch

These two seems interesting to include indeed.

re-pacman (needs some updates? [2])

Well, I already didn't like this script in the first place, I found the idea ugly. I still had a look at it to check if it worked. And I see the implementation is ugly as well, since it's based on -Qi output. If you take a few steps back, what's happening is so stupid (I'm not blaming any one here, or maybe only me for not being able to provide patches) : makepkg creates the .PKGINFO files repo-add transform the .PKGINFO to desc/depends pacman -Si/-Qi interprets the desc/depends file and display the info re-pacman looks at -Qi output and try to translate it back to .PKGINFO ... Just one example, the build date is stored as unix epoch, but pacman displays it in human readable way. However, we are lucky here, since date is apparently able to convert it back : 39 >-builddate=$(pacinfo ${1} 'Build Date') 40 >-echo "builddate = $(date -d "$builddate" +%s)" The build date could be the date of today though. Now if we try do to the same for size field, it will get uglier. But here again, we could compute the current size taken, which might have changed. Empty fields in pacman -Qi output should be dealt with too (for example Groups = None). Anyway, if you want an accurate re-pacman, you need to check the .PKGINFO creation in makepkg, and find out how to get that back from pacman -Q output. Or change re-pacman to use directly the files in /var/lib/pacman/local/ And maybe before that, change the local database to use .PKGINFO format, to ease up re-pacman task :) I have no interest in updating re-pacman though, because I don't use it and find it useless (even though I recognize it might be handy and practical in some cases, I still don't like it).

wget-xdelta.sh

We don't need this anymore in the git repo, do we?

vim: PKGBUILD.vim

That looks interesting for detecting some stupid errors / typos in PKGBUILDs. The colors are still nearly the same as in sh, except that it highlights the errors it finds in PKGBUILD fields.

vimproject (needs updated - developer use only)

Indeed, this is only useful when you already have the whole source, so no need to package it.

On Thu, Feb 21, 2008 at 7:19 AM, Dan McGee wrote:

On Thu, Feb 21, 2008 at 5:54 AM, Xavier wrote:

...

...

re-pacman (needs some updates? [2])

Well, I already didn't like this script in the first place, I found the idea ugly. Not the biggest fan either, but might as well include it if it works. Sounds like it needs some patching though.

re-pacman was a one-off script that someone had asked me for. In essence it'd let you repackage your current configs in the package, so it has a bit of a neat factor.... but still, I've never once used it

On Fri, Feb 22, 2008 at 7:10 PM, Allan McRae wrote:

Hi,

I've put a pacman-contrib package into AUR. Will probably move into community in the near future.

At the moment it contains pacsearch, pacdiff and vim PKGBUILD syntax files.

I actually like the idea of re-pacman but it needs work before I will include it. I could find no colour pacman scripts that pacsearch is not a replacement for. I'm holding out on including anything to do with repo cleaning on a decision on what will happen in pacman or someone who uses such a script to submit it to git...

Side note: Once you move it to community, feel free to delete my pacsearch package I have in AUR- it is probably outdated anyway compared to the current one in the pacman repository. -Dan

Xavier wrote:

...

Well, I already didn't like this script in the first place, I found the idea ugly. I still had a look at it to check if it worked. And I see the implementation is ugly as well, since it's based on -Qi output. If you take a few steps back, what's happening is so stupid (I'm not blaming any one here, or maybe only me for not being able to provide patches) : makepkg creates the .PKGINFO files repo-add transform the .PKGINFO to desc/depends pacman -Si/-Qi interprets the desc/depends file and display the info re-pacman looks at -Qi output and try to translate it back to .PKGINFO ...

Just one example, the build date is stored as unix epoch, but pacman displays it in human readable way. However, we are lucky here, since date is apparently able to convert it back : 39 >-builddate=$(pacinfo ${1} 'Build Date') 40 >-echo "builddate = $(date -d "$builddate" +%s)"

The build date could be the date of today though.

Now if we try do to the same for size field, it will get uglier. But here again, we could compute the current size taken, which might have changed.

Empty fields in pacman -Qi output should be dealt with too (for example Groups = None).

Anyway, if you want an accurate re-pacman, you need to check the .PKGINFO creation in makepkg, and find out how to get that back from pacman -Q output. Or change re-pacman to use directly the files in /var/lib/pacman/local/ And maybe before that, change the local database to use .PKGINFO format, to ease up re-pacman task :)

I have no interest in updating re-pacman though, because I don't use it and find it useless (even though I recognize it might be handy and practical in some cases, I still don't like it).

I just found this : http://foulmetal.free.fr/archlinux/repacman-0.98.tar.gz

This one uses the depends / desc files from the local db, but I didn't look at anything else. So just in case anyone is interested by this repacman stuff, there is a different version from the one in pacman/contrib/.

Hm. I may have missed something, but where can the end-user find the original re-pacman? I've just checked, it is not part of pacman-contrib package. Bye

Xavier wrote:

Nagy Gabor wrote:

...

Hm. I may have missed something, but where can the end-user find the original re-pacman? I've just checked, it is not part of pacman-contrib package.

Well, I thought it still needed to be reviewed and completed / fixed / updated. Afaik, no one did any work on it.

Thats right. I did not included it in the pacman-contrib package because it needed reviewed/updated and I never got around to it.... It is still on my todo list but at a low priority so if anyone else wants to do this.... Allan