Re: need help making a port for django

On 5 sep 2006, at 17.33, Jordan K. Hubbard wrote:

> FWIW, I think we should go with just one version of any port  
> (whatever version is deemed most appropriate) and only add other  
> versions when and if it becomes clear that they're actually  
> needed.  Django may have broken compatibility for the last 3  
> releases, but given that MacPorts has no actual users of Django  
> yet, the whole "backwards compatibility" argument is slightly  
> suspect and would be far more applicable if MacPorts had been  
> tracking Django all along.

I've actually refrained from filing tickets for Django since I sort  
of foresaw this problem. I'm still of the opinion that having a set  
of versioned ports maintained, for the benefit of users not having to  
go to an outside source when a port leave them behind is a worthy goal.

But then of course I don't have the perspective for assessing a  
coherent ports tree...

To align Django with the rest of the tree I'd keep -devel. Then let a  
proper Django port wait for the 1.0 release when there is a firm  
commitment to not break backwards compatibility from the upstream  
developers.

- Daniel