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
Task Type Bug Report
Category Dashboard
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 1.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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!
Comment by eliott (cactus) - Friday, 31 August 2007, 07:11 GMT
I think this change may be more complicated than it at first seems.
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.
Comment by Paul Mattal (paul) - Thursday, 24 September 2009, 11:35 GMT
I think I agree, but wonder if the arch world has evolved substantially the other way for arch packages in the intervening 2 years since this first discussion.

What do you think? Is this still worth pursuing?
Comment by Paul Mattal (paul) - Thursday, 24 September 2009, 11:42 GMT
I admit it's always bugged me that testing packages have "no maintainer". Really just an artifact of this same conceptual bug.

Loading...