Update: py25-django-devel, py-django-devel

[ebgssth@…]

Updated Portfile for 0.96.1, the latest Django.

[ebgssth@…]

python2.5

[ebgssth@…]

python2.4

[ebgssth@…]

BTW, 0.96.1 is not development version. So I think "-devel" suffix of the port name is kind a weird to me.

[ryandesign@…]

The reasoning for the -devel naming is explained in the commit message for r19418. I don't know if that reason still applies.

[erickt@…]

I added this because django has the policy of not maintaining a backwards compatible api until they hit 1.0, which they haven't hit yet. So, I added the -devel to make it clear to end users that it could change underneath them and break their code.

[ebgssth@…]

Replying to erickt@macports.org: I see. But I hope MacPorts has branches as in debian's apt system.

[ebgssth@…]

Any update on this?

[ebgssth@…]

Is there anyone working on this? no info provided more than two weeks...

[stechert@…]

I did the version update long ago, but couldn't close the ticket because I only own one of the portfiles. I think this is actually three tickets: (1) update py25-django-devel, (2) update py-django-devel, and (3) decide what's going on with the -devel names. If you break it out that way, I'd be happy to go ahead and close (1), which is the part that I'm responsible for. If someone makes a decision on the devel thing, I'm happy to engage on that for the py25 version, but until then, I think I've done what I needed to do.

[erickt@…]

Oh, I'm terribly sorry. I thought someone had taken over py-django-devel from me, but I guess not completely. I've committed this as well. Stechert, feel free to add yourself to py-django-devel if you want. I'm not sure what to do about -devel though.

[ebgssth@…]

Both django ports are now the latest release. Close this ticket please?