| From: | Ray A. Akey |
| Date: | 24 Aug 2000 at 04:31:10 |
| Subject: | Re: AMIOPEN: Amiga tool inclusion... |
"Martin Baute" <solar@baud.de> wrote:
> Hello Ray
> > Uploads containing readmes that do not conform to a predetermined set of
> > headers simply will not be made available for download.
>
> The HTTP form can easily be configured to reject incomplete forms.
..as I already said. :)
> I guess you don�t want to check every FTP upload manually. A
> checker for FTP uploads can check the .readme for completeness,
> and send out an e-mail to the uploader if minimum criteria are not
> met. If no uploader e-mail is given, bad luck.
Eventually, this is the plan.
> But: What about ports? I have seen several ports of non-Amiga
> software on Aminet which have _two_ versions - one for the
> version of the original program (like e.g. v5.7 for RCS) and one
> for the Amiga port (HGWRCS 20, thanks a lot Heinz!). Any idea
> for this? Like an additional "Port Version:" field?
All we really need be concerned about is the Amiga version. The reason for
the version numbers here are to let the users know an AMIGA version is newer
than what they have installed. Developers already know what they have and/or
are working on. And for those that need the "dirty details", you can always
include the extra info in the body of the .readme.
We do not want to get trapped in the mire of complicating things for the
casual developer who wants to upload his/her software so let's go easy on
these header requirements and "KISS"..
Subscribe/Unsubscribe: open-request@amiga.com
Amiga FAQ: http://www.amiga.com/faq.html