Automatic homepage for sourceforge, googlecode, etc.

[Scott Haneda]

Simplify the base code, or simplify the port files?  The port files  
list a url, which I find highly readable, and also nice, because I can  
easily know what that url is, and ping, curl, or http request it.

It seems to me the base MacPors code would only become more complex  
(trivially), as now you have to maintain a mapping of master_sites to  
names/url's.  Yes, it is a trivial mapping.

I would think it could not hurt, and may be useful to some, and there  
is always the option of simply hard coding the url in if you are so  
inclined.  However, from a port maker perspective, I am somewhat  
partial to using real url's, as they are easier for me to debug and  
know at a glance, what is going on.

My .02

On Aug 22, 2009, at 10:37 AM, Ryan Schmidt wrote:

> For projects hosted on SourceForge or Google Code or other common  
> sites we have simple ways of expressing the master_sites:
>
> master_sites sourceforge
>
> master_sites googlecode
>
>
> This also automatically sets the livecheck.
>
>
> Wouldn't it be useful to be able to do that for the homepage as  
> well? Currently ports have to manually specify
>
> homepage http://${name}.sourceforge.net/
>
> homepage http://code.google.com/p/${name}/
>
>
> Could we simplify it like this?
>
> homepage sourceforge
>
> homepage googlecode
>
>
> Or maybe the homepage would also automatically be set if  
> master_sites uses one of those shortcuts?
>
>
>
> Now that I think about it, the way these shortcuts are working now  
> is a little like portgroups. In fact all of it probably could be  
> implemented as a portgroup.
>
> PortGroup sourceforge 1.0
>
> PortGroup googlecode 1.0
>
> Might that simplify base code a bit?

-- 
Scott * If you contact me off list replace talklists@ with scott@ *