addon-kit
."--
You received this message because you are subscribed to the Google Groups "mozilla-labs-jetpack" group.
To post to this group, send email to mozilla-la...@googlegroups.com.
To unsubscribe from this group, send email to mozilla-labs-jet...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mozilla-labs-jetpack?hl=en.
The solution that almost always work for me is the following:
1) I have a symlink in the packages dir of my addon:
myAddon/packages/myOtherPackage -> ~/Projects/myOtherPackage
2) In the packages.json, I add the following property:
dependencies: "api-utils,addon-kit,myOtherPackage"
And that does the job.
Hernán
IMO, they are work-arounds but not particularly friendly ones. The SDK
really should be able to stand-alone and not require a build process to
locate and modify it.
I assumed --package-path exists in an attempt to support packages
external to the SDK - or have I missed the point of that option?
Mark
> On 20/06/2011 7:55 PM, Irakli Gozalishvili wrote:
>> Option 1:
>> Option 2:
>
> IMO, they are work-arounds but not particularly friendly ones. The SDK
> really should be able to stand-alone and not require a build process to
> locate and modify it.
>
> I assumed --package-path exists in an attempt to support packages
> external to the SDK - or have I missed the point of that option?
Yeah, --package-path is intended to do just that. I implemented it to
point to a directory *containing* packages, rather than pointing
directly at the extra packages, because 1: it was slightly easier, and
2: that's how it tends to work in other languages/environments: e.g.
$PYTHONPATH in Python, $PERL5LIB in Perl, and -I/-L/$LD_LIBRARY_PATH in
gcc. A consequence is that you have to maintain a library directory with
just packages in it.
Your --package-path-points-to-a-package patch (say that 5 times fast!)
is intriguing.. I gotta think about that one. There are two things that
it might interact with. One is that, at least in theory, packages can
contain subpackages. The other is that --package-path is actually a
comman-separated list of directories, so we should make sure it can
handle that (iterate through each one, look for a package.json, either
add the package directly or scan its subdirectories for packages).
Definitely file a bug on that, and copy me (:warner), so I don't forget
about it.
cheers,
-Brian