FS#3024 - Upload Warnings and Errors Distinction

Attached to Project: AUR web interface
Opened by dtw (dibblethewrecker) - Monday, 01 August 2005, 14:59 GMT
Last edited by Callan Barrett (wizzomafizzo) - Thursday, 27 March 2008, 09:12 GMT
Task Type Feature Request
Category Backend
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 1.1
Due in Version 2.0.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

i.e. any tarball that contains a file called *.pkg.tar.gz

and, my pet hate at the moment, any tarball that contains the filelist file
This task depends upon

Closed by  Callan Barrett (wizzomafizzo)
Thursday, 27 March 2008, 09:12 GMT
Reason for closing:  Won't implement
Comment by dtw (dibblethewrecker) - Monday, 01 August 2005, 15:00 GMT
Sorry this should be a feature request!
Comment by Simo Leone (neotuli) - Friday, 12 August 2005, 04:42 GMT
We can't blanket like that. There may at times be a legit reason for doing something like that. What we CAN do is put in a warnings-fashion system where the user receives warnings about things like that, rather than a flat out rejection.

Other things that go on warning list: pkg/ src/ filelist, certain things in PKGBUILDs.

Comments? We can hack this in in 1.X but I'd like to see it for sure in 2.0.
Comment by dtw (dibblethewrecker) - Monday, 15 August 2005, 19:21 GMT
I can't see a case for including a filelist or a binary pkg in any AUR submission - is that just me? Surely a binary pkg in the UNSUPPORTED is a bad situation?

As for the filelist, could that not be deleted if present when the tarball is rebuilt?
Comment by Simo Leone (neotuli) - Monday, 15 August 2005, 21:03 GMT
How can you garauntee that filtering everything ending in .pkg.tar.gz is a binary package file? In general, in our arch world, yes, that's how it is, but there's no way to know for sure. As for filelist, well, currently the main Arch interface generates a filelist of binary packages so that you can search for files within packages. Now I know that the AUR is just PKGBUILDs, but my thinking is that forcing people to include a filelist actually wouldn't be a terrible idea, so people know what to expect.

For the time being, people simply shouldn't include them, I think the issue is open to debate though, as it can be handy to have a filelist on hand too.

Maybe that's just my warped thinking though :X
Comment by dtw (dibblethewrecker) - Monday, 15 August 2005, 22:49 GMT
How can you garauntee that filtering everything ending in .pkg.tar.gz is a binary package file?

You can't. But I think it is better to verbosely reject the one or two occasions when it is legitimate, than to leave the system "wide open".

Seeing as you have to build teh file yourself you can get your own file list if you really want it...it's just cruft to me. Still...1k per file 1000 files < 1Mb - hardly something to lose sleep about.

Loading...