H. Peter Anvin wrote:
> Keith Kanios wrote:
>
>>>
>>>
>> Yep, I currently have the login and access.
>>
>> No, the website is not done through CVS (anymore?).
However, you can
>> upload/download through SSH... as that is what I
have been doing.
>>
>> I've updated the site to reflect the latest info.
>>
>> As for "we need to figure out how best to get
the version numbers on the
>> webpage updated"... *Statically*, just keep
updating the index page.
>>
>> *Dynamically*, SF supports PHP. With PHP, you can
have the front page
>> pull a version number from somewhere... even from
one of the git pages
>> like http://repo.or.cz/w/nasm.git?a=blob_plain;f=version;h
b=HEAD
>> *****BUT***** SF actively denies remote socket
connections through PHP.
>> The only quick and reliable (non client-side) way
around this, short of
>> getting/using your own hosting provider (possible
redirect to
>> zytor.com/nasm???), is to manually upload the
"version" file to the
>> htdocs root and have the index page parse that file
for the number.
>>
>> I don't have the time to contribute to NASM
anymore, but I am still on
>> the dev list and I can keep the web pages updated
upon request... just
>> make the subject line obvious for quicker responses
;)
>>
>> Good job with NASM, keep it up 
>>
>>
>
> Sounds like the easiest way to deal with this is to
just use the PHP to
> include a file with the version number which we can
simply scp up at the
> time we upload a new release.
>
> -hpa
>
Done. Just upload a new "version" via SSH/SCP to
htdocs with each new
release and everything is a go
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nasm-devel mailing list
Nasm-devel lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nasm-devel
|
