django - 1.0.2 - does not follow slotting conventions

[krunk7@…]

All versions of django ports install a script named: django-admin.py into /opt/local/bin.

This causes conflicts between different versions, e.g. py26-django & py25-django

--->  Installing py26-django @1.0.2_0
--->  Activating py26-django @1.0.2_0
Error: Target org.macports.activate returned: Image error: /opt/local/bin/django-admin.py is being used by the active py25-django port.  Please deactivate this port first, or use the -f flag to force the activation.

Suggestion:

In the post-destroot or destroot phase, rename conflicting scripts with slot version. E.G. django-admin26.py or some such.

[mf2k (Frank Schima)]

In the future, please use the proper WikiFormatting.

[arthur@…]

You're right but renaming the script to "django-admin$VERSION.py" would make the bash-completion unusable because the completion script explicitly checks for a file named "django-admin.py". This needs a custom patch applied to the bash-completion file which changes the checks for "django-admin.py" to the new version specific filename of the script.

[krunk7@…]

Replying to arthur@…:

You're right but renaming the script to "django-admin$VERSION.py" would make the bash-completion unusable because the completion script explicitly checks for a file named "django-admin.py". This needs a custom patch applied to the bash-completion file which changes the checks for "django-admin.py" to the new version specific filename of the script.

If python_select were updated to create a sym link from django-admin.py to the modified one, django-admin26.py or some such, wouldn't bash-completion still work?

[arthur@…]

This will be fixed once #18903 is commited.

[mf2k (Frank Schima)]

Cc Me!

[arthurk@…]

Fixed in r48732, r48733 and r48734

[(none)]

Milestone Port Bugs deleted