FS#7787 - {archweb} Architecture independent package information
Attached to Project:
Arch Linux
Opened by Aaron Griffin (phrakture) - Sunday, 12 August 2007, 04:26 GMT
Last edited by Dan McGee (toofishes) - Friday, 03 September 2010, 06:09 GMT
Opened by Aaron Griffin (phrakture) - Sunday, 12 August 2007, 04:26 GMT
Last edited by Dan McGee (toofishes) - Friday, 03 September 2010, 06:09 GMT
|
Details
Yes, this is a bug report. Our dashboard should not be
driven by architecture at all. The package itself should be
"king".
Some package "foo" should link to architecture specific details. For instance, the front end should be able to list what architectures contain "foo", the versions in that architecture, and additionally allow people to become the maintainer for only one architecture or all architectures. |
This task depends upon
Closed by Dan McGee (toofishes)
Friday, 03 September 2010, 06:09 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed. Oldest bug open at the moment in the Arch Linux project!
Friday, 03 September 2010, 06:09 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed. Oldest bug open at the moment in the Arch Linux project!
It would effectively create n versions of a package in the backend database, where n is the number of arches supported. I say this becuase I believe the repo and build system are using the same database, and would have to be retrofitted in conjunction with the change to the web interface.
Not 100% sure on that, since I haven't poked into some of the darker crevasses of the packaging infrastructure.
What do you think? Is this still worth pursuing?