Re: need help making a port for django

No, thats a good question. It all really depends on MacPorts, and their 
policy with backwards compatibility. I ran into this issue before with 
another one of my packages, py-scipy. It's unclear how we should go 
about updating packages that result in incompatibilities. For the larger 
projects, such as gtk, it makes sense that we keep around gtk1 while 
supporting gtk2. For smaller packages though, it's hard to tell when we 
should, and should not, support older versions.

Any of the senior MacPorts folks around to resolve this policy decision? 
I personally don't mind doing either, I just personally don't want to 
make a call that could potentially break other people's stuff. So, could 
you? :)

-e


Jordan K. Hubbard wrote:
> Hmm.  Could you explain to those of us less django-inclined just why 
> we need 4 separate versions of this one?   If there's a really good 
> reason then cool, just asking, but I'm sure you can also see how this 
> approach to all ports really wouldn't scale...
>
> Thanks,
>
> - Jordan
>
> On Sep 4, 2006, at 11:24 AM, Erick Tryzelaar wrote:
>
>> Thanks Daniel and Mark!
>>
>> I've checked in py-django090, py-django091, py-django095, and 
>> py-django-devel (uses a specified version from subversion, currently 
>> 3712).
>>
>> -e
>> _______________________________________________
>> Darwinports mailing list
>> [email protected]
>> http://www.opendarwin.org/mailman/listinfo/darwinports
>
> _______________________________________________
> Darwinports mailing list
> [email protected]
> http://www.opendarwin.org/mailman/listinfo/darwinports