You are not logged in.
You can read all about the new release here.
This thread is for comments and other general talk about the newest pacman release. This is not a bug reporting venue. Inquiring here if other people have the same problem as you is fine, but know that your problem will not be fixed by complaining about it here. Please file a proper bug report under the 'Pacman' project.
Offline
I'd like to simply say that I've been using pacman 3.2.0 since it hit testing, and it's been working wonderfully. However, I admittedly do not ask much of pacman.
All in all - great work guys. Works well here.
"Unix is basically a simple operating system, but you have to be a genius to understand the simplicity." (Dennis Ritchie)
Offline
Thanks a billion for the AND searches!
Offline
I have questions about the removal of pacman.static:
I have installed Arch from within another Linux environment with the help of pacman.static.
Now that it's dropped, do I have to build it myself on another system, which might not include all necessary developmental tools or will there still be a way to obtain a pre-compiled static version?
What is now the recommended way of repairing the system in case of for instance removing libc accidentally?
Just for the record: Yes, I have noticed that pacman depends now amongst others on libbz2 and libz, which would increase the size of a statically build library due to increased functionality.
Last edited by wuischke (2008-08-07 15:08:08)
Offline
Thanks a billion for the AND searches!
+1 And thanks ibendiben for this post because i read over it in the first moment.
Offline
ibendiben wrote:Thanks a billion for the AND searches!
+1 And thanks ibendiben for this post because i read over it in the first moment.
Ahah, it is funny how a very small amount of work can get some attention, 5 lines changed :
http://projects.archlinux.org/?p=pacman … 07b63904b9
and a huge amount of work like the switch to dynamic allocation gets not so much :
http://projects.archlinux.org/?p=pacman … f63d7cfc26
http://toofishes.net/blog/valgrind-330-and-new-massif/
Poor Dan Just kidding, this memory improvement was for sure the greatest change of 3.2, even though it is hardly noticeable as an user, without looking closely at the mem usage.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Ahah, it is funny how a very small amount of work can get some attention, 5 lines changed:
I can only speak for me and before this change i do "pacman -Qs | grep search 1 | grep search2" and than a "pacman -Qi result" only to read the description. Now it is possible to do it in one step.
and a huge amount of work like the switch to dynamic allocation gets not so much:
Ok, this is hard to understand.
Offline
Thanks a billion for the switch to dynamic allocation!
Offline
But... I wanna cry....
Plz ppl, can somebody tell me how I'm going to install arch from slax applying my mkfs-then-mount-then-chroot-then-reboot technique?
RIP pacman.static, may /dev/null be with you...
They say that if you play a Win cd backward you hear satanic messages. That's nothing! 'cause if you play it forwards, it installs windows.
Offline
But... I wanna cry....
Plz ppl, can somebody tell me how I'm going to install arch from slax applying my mkfs-then-mount-then-chroot-then-reboot technique?
RIP pacman.static, may /dev/null be with you...
Provide a PKGBUILD in the AUR for pacman.static. Make a package, or just create a tarball with pacman.static in it.
The point Dan makes is that pacman.static in an Arch package is near useless. If you use it to install from another distro then why do you need the pacman package?
I'm sure someone could easily provide a pacman.static build for people to use, and stick the info in the wiki.
Offline
QSL, mr. overlord. QTC successfully recieved
They say that if you play a Win cd backward you hear satanic messages. That's nothing! 'cause if you play it forwards, it installs windows.
Offline
-A option removed ? How can I install now a local package from my box ?
Offline
-A option removed ? How can I install now a local package from my box ?
-U, --upgrade
Upgrade or add a package to the system. Either a URL or file path can be
specified.
flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)
Offline
attila wrote:ibendiben wrote:Thanks a billion for the AND searches!
+1 And thanks ibendiben for this post because i read over it in the first moment.
Ahah, it is funny how a very small amount of work can get some attention, 5 lines changed :
http://projects.archlinux.org/?p=pacman … 07b63904b9
and a huge amount of work like the switch to dynamic allocation gets not so much :
http://projects.archlinux.org/?p=pacman … f63d7cfc26
http://toofishes.net/blog/valgrind-330-and-new-massif/Poor Dan Just kidding, this memory improvement was for sure the greatest change of 3.2, even though it is hardly noticeable as an user, without looking closely at the mem usage.
This is similar to the reasons KDE4 has got so much criticism (aside from the fact that everyone wrongly thought KDE4.0 was _the_ release). People can't care less about the new API's and frameworks like phonon, decibel and solid. What they care about is whether the panel can be hidden or whether icons can be put on the desktop. Visible elements are _always_ the major pulling factors when considering the general population.
Take the kernel. New driver added for intel3945 wireless card, mass hysteria! Typesafe callbacks, no one gives a crap!
Although I guess who can blame the general population. Everyone wants something that works and has the features they want, and it doesn't matter how it's done. Who cares about making things easier to code and more flexible for the future. If it doesn't work now, it's rubbish. Hmmm, I seem to be ranting about KDE4 again. Apologies
flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)
Offline
Ahah, it is funny how a very small amount of work can get some attention, 5 lines changed :
http://projects.archlinux.org/?p=pacman … 07b63904b9
and a huge amount of work like the switch to dynamic allocation gets not so much :
http://projects.archlinux.org/?p=pacman … f63d7cfc26
http://toofishes.net/blog/valgrind-330-and-new-massif/
Dynamic what? I always appreciate the improvement of things that I don't understand. Thankfully, others do. So thanks!
/path/to/Truth
Offline
attila wrote:ibendiben wrote:Thanks a billion for the AND searches!
+1 And thanks ibendiben for this post because i read over it in the first moment.
Ahah, it is funny how a very small amount of work can get some attention, 5 lines changed :
http://projects.archlinux.org/?p=pacman … 07b63904b9
and a huge amount of work like the switch to dynamic allocation gets not so much :
http://projects.archlinux.org/?p=pacman … f63d7cfc26
http://toofishes.net/blog/valgrind-330-and-new-massif/Poor Dan Just kidding, this memory improvement was for sure the greatest change of 3.2, even though it is hardly noticeable as an user, without looking closely at the mem usage.
It's ironic that one of the hardest things in programming is to make a *major* change and not have it show. The fact that we users don't notice the change actually means that it was a huge success. Thank you Dan, shining and all the pacman contributors. Great job!
Offline
kjon wrote:But... I wanna cry....
Plz ppl, can somebody tell me how I'm going to install arch from slax applying my mkfs-then-mount-then-chroot-then-reboot technique?
RIP pacman.static, may /dev/null be with you...
Provide a PKGBUILD in the AUR for pacman.static. Make a package, or just create a tarball with pacman.static in it.
The point Dan makes is that pacman.static in an Arch package is near useless. If you use it to install from another distro then why do you need the pacman package?
I'm sure someone could easily provide a pacman.static build for people to use, and stick the info in the wiki.
I didn't have the time to look at doing a static build, but here's an alternative that might be useful: package the dynamic binary with all the libraries it needs.
My version uses a shell script called pacman to run the pacman binary explicitly with the correct libraries. You can get the source using:
svn export http://svn.berlios.de/svnroot/repos/lar … man-packed
A ready-built package (just a tar-ball, not an Arch package) is available at:
ftp.berlios.de/pub/larch/larch5.3/i686/pacman-packed.tar.gz
As you might guess, I did this for use in larch, but it could be easily tweaked for other purposes ...
Still, if anyone has got a script to resurrect pacman.static I would be interested.
larch: http://larch.berlios.de
Offline
It's ironic that one of the hardest things in programming is to make a *major* change and not have it show. The fact that we users don't notice the change actually means that it was a huge success. Thank you Dan, shining and all the pacman contributors. Great job!
Hehe, that is perfectly true
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Offline
Pacman 3.2.1 just landed in testing. The biggest fixes are a handful of changes to makepkg, along with a segfault fix on x86_64 when using UseSyslog. Please report any problems to the usual avenues- the bug tracker or the pacman-dev mailing list.
Offline