Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#4962 - Don't switch to mysql-based package manager.
|
DetailsI will quote myself in this thread for simplicity:
http://bbs.archlinux.org/viewtopic.php?p=175565#175565 "Also i'm not sure if I like the new mysql db way pacman 3 takes, when a flat db works great and fast enough the 'pacman-drive' way. I'm concerned this will introduce new bugs in pacman and continually be dependent that mysql doesn't fsck up... which isn't very KISS in my opinion." it ofc also introduces a new dependency which is mysql of which i don't know how well will work with live-cd's and similar, but maybe this is an unjustified concern. I HOPE that the pacman 3 devs still will consider the 'pacman-drive' approach even though mysql is implemented in CVS. As after all, i'm hope that what we all want is the best possible archlinux and that we won't destroy archlinux with too hasty decisions and implementations. |
This task depends upon
Comment by Judd Vinet (judd) -
Tuesday, 04 July 2006, 22:43 GMT
Not sure where you got this information, but there is no mysql-db code in the pacman3 codebase. We've talked about something faster, like a sqlite backend, but haven't arrived at any final decisions yet. As it stands now, the pacman3 codebase still uses flatfiles for the backend and is fully compatible with a pacman2 installation.
Comment by Judd Vinet (judd) -
Tuesday, 04 July 2006, 22:43 GMT
And I think we both know that this isn't a critical bug report. Hmmmmm? :)