Your solution for javascript-common works for me and maintains
nomenclature.
- Marc
Marc J. Driftmeyer
[EMAIL PROTECTED]
http://www.reanimality.com
(509)435-5212
On Apr 7, 2008, at 3:01 PM, Steve Kemp wrote:
Hi,
Thanks for the report.
(I've reassigned this bug to the 'javascript-common' package
which is the one which actually makes the global /javascript/
alias.)
You raise an interesting point here. The /javascript/ alias
could indeed be used by people who wish to use the jquery package,
and if that is the case then there will be breakage.
There are two possible solutions to this bug:
1. Do nothing. Rely upon the end user (you in this case) to
remove the global alias, and change it to their own if they
spot the collision.
2. Change the default for the javascript-common. I'd actually
suggest we use /javascript-common/ as the alias, rather than
your suggestion of '/javascriptlibs'. That matches the package
name, if not the directory.
I've no strong preference on the way forward here, but I'd slightly
lean towards the first option. I can see that it could cause users
pain though; so the second would be acceptible. I just fear that
whatever "new name" we pick for the alias will be taken by
*somebody*.
So its the lesser of two evils: Leave as-is, so that people using
the package already don't get suprised, or change it and still run
the risk of a collisions - and a new bug report from a different
user..
Steve
--
Managed Anti-Spam Service
http://mail-scanning.com/
