FS#1024 - prepare for other architectures
Attached to Project:
Pacman
Opened by Dale Blount (dale) - Wednesday, 23 June 2004, 21:07 GMT
Last edited by Judd Vinet (judd) - Saturday, 18 September 2004, 03:16 GMT
Opened by Dale Blount (dale) - Wednesday, 23 June 2004, 21:07 GMT
Last edited by Judd Vinet (judd) - Saturday, 18 September 2004, 03:16 GMT
|
Details
now's probably as good as time as any to start preparing for
other architectures... 64bit cpus will be commonplace soon,
and we're still getting i586 and even ppc requests (I have
both 586s and a ppc, and a 64bit soon hopefully for
testing).
the current/release/stable symlinks would have to change to point to 0.x/os/ and pacman.conf would have to point to ftp://ftp.archlinux.org/current/i686 for 686, etc. we might even want to consider adding the arch in the pkg file name like other distos do so people don't go trying to install i686 packages on their ppc. |
This task depends upon
This was my main reason for adding the Architecture field to package meta-info. You can query a package's architecture by looking in the -Qi output.
# pacman -Qip pkgfile.pkg.tar.gz
It would be nice to have that info in the package name itself, but it will be a lot of work.