[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gpsd-users] Problems with the gpsd website move

From: Eric S. Raymond
Subject: [gpsd-users] Problems with the gpsd website move
Date: Sun, 26 Feb 2012 01:51:50 -0500
User-agent: Mutt/1.5.21 (2010-09-15)

Note: I'm moving this thread from the Berlios mailing users list  
to the two new lists at Savannah (dev list added because I want my 
lieutenants Chris Kuethe and Gary Miller, and other senior devs such as 
Bernd Zeimetz, in on the discussion). Please do not use the Berlios lists.

Tomalak Geret'kal <address@hidden>:
> *still* ranks the highest on Google when searching
> for "gpsd". Since it allegedly officially shut down at the end of
> last year, I see this as a potential problem.
> Should the old site not respond with 301 "Moved Permanently" now,
> rather than the human-readable statement? Information about the site
> move can be provided prominently on the new site that the user will
> end up on, and hopefully this will help to fix search results (I
> believe?)

I'd do that, but for the fact that the new site location may *not* be

The reason the GPSD web pages are now on my personal site is not because
I want them to live there, but because modifying project webspace on Savannah
is a huge, huge pain in the ass.  

The Savannah admins think they need to avoid giving users direct rsync
or scp access to the web host machine for security reasons. So the
only way they give you to modify your Savannah webspace is to check
the page changes into a per-project CVS repo, which is periodically
scraped by a cron job that moves the chasnges to where they're

I moved the project in a hurry. In order to avoid dealing with that CVS 
crap I parked the website in my webspace on ibiblio.  At this point I 
see the following options:

1) Write a script that will push changes through Savannah's narrow, twisty
CVS-centered procedure and move the website there.  Advantage: all our stuff
would live at a permanent location on Savannah.  Disadvantage: the damn 
cron-job delay. I hate the fact that after updates I'd have to wait an unknown
amount of time for the changes to be visible.

2) Leave it where it is. Advantage: Website updates remain fast and cheap.  
Disadvantage: webpage URLs don't have any connection with the project
URL except through my name, and nobody except me can update the website.

Anyone got any creative ideas?
                <a href="";>Eric S. Raymond</a>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]