> On Tue, 2008-06-17 at 10:51 -0700, scott mc wrote: >> There's a couple annoying issues with the downloads plugin. One is >> that when I try to add a new file, the add form appears on top of >> other text, making it hard to read, I filed ticket #61 on the new site >> for this so that I could attached a screenshot to it. > > I noticed this too. You can avoid this by making your browser window > wider though (quite extremely wide, though). > Can you file a ticket at trac-hacks for this? I don't think I have the > time to dig into the download plugin code. I'm very busy lately, and I > have some bug-fixing to do for the PortLogPlugin. > Reported: http://trac-hacks.org/ticket/3208 Looks like I need to follow up on it, as they replied back with more questions... Seems the PortLogPlugin is different since the last time i used it. I added port logs for each of the binaries currently posted in the downloads section, but didn't see all the options that were there before. I take it that it's a work in progress so I'll let it slide ;) I noticed that you CAN sort the downloads, just click on the header link for the column you'd like to sort by. Adding in the portlog entries for each of the listed downloads did fix the component thing like you said it would, so that's better now. >> Second is that >> the component list box only has a limited number of items, I hope this >> is to be fixed before the move over. > > Components correspond to the ports that are in the database. You will > have to use the AddPort form to add the port to the database. > >> I've started uploading a few files on there now, using the make >> install DESTDIR=/boot/foo trick and then running zip -ry9 >> foo-haiku-x.x.x.zip. >> It would be nice if that download list was sortable, I supposed once >> it grows to be a few hundred or more files it's probably going to get >> messy. > > True. But also here, the download plugin would have to be altered. > Perhaps it is a good idea to look for an alternative to this plugin? IMO > it would be best if all the bin archives were to be stored on an FTP > with directories corresponding to the port categories. > >> I think for the file name foo-bin-x.x.x-haiku-r.zip or something along >> those lines might work better than the one I am using now. Where v >> would be the revision of the zip file, so if say we've found a better > > I suppose you mean 'r', not 'v'? yeah, I had v there then realized it should be r but didn't change them all it seems. I think we can leave out the bin, and only put something in there if it's not a bin, such as foo-src-x.x.x-haiku-r.xip > >> way to build a specific package but it's release version didn't >> change, we would bump up the r# number to show that it's a different >> haiku build then the previous r#. > > Please include the port revision number too, as I proposed in 'Re: > PortLogPlugin and the new host'. While there's no strict revision > numbering at this moment, the new site will enforce this. > How's this format? foo-x.x.x-haiku-r.zip where foo is the port name, x.x.x is the port version, haiku/beos/zeta/bone is the platform, r is the portlog revision number. -- BePorts homepage - http://tools.assembla.com/BePorts List archives: //www.freelists.org/archives/beports Administrative contact: brecht@xxxxxxxxxxx