I'm developing a plugin for SublimeText that uses the FullScreenStatus plugin. Is there a way to set it up so that if someone installs my plugin, the FullScreenStatus plugin will be automatically installed as well, like a requires directive? Every other package manager I know of can do this, but I couldn't find anything in the docs and no other package I looked at is trying to require another package.
Since FullScreenStatus is MIT licensed, I could just include it in mine, but is there a way to require it without doing that?
You either have to bundle it yourself, or explain in the install message and README there is an external dependency. If you feel like adding to the discussion on dependency management, feel free to contribute to https://github.com/wbond/sublime_package_control/issues/166. Some initial work can be seen at https://github.com/wbond/sublime_package_control/issues/291#issuecomment-14028788.
Related
I consider migrating a project to Apache Jena but can't get my mind around Jena's architecture. In this example...
https://github.com/apache/jena/tree/master/jena-permissions/src/example/java/org/apache/jena/permissions/example
... we make use of the "permissions" package.
But when I try to imitate what they do in the example using Eclipse and importing the *.jar files from apache-jena-3.1.1 as dependencies, the package org.apache.jena.permissions seems to be missing or inaccessible. Other packages such as org.apache.jena.rdf.model are accessible.
How can I access this package? Thank you very much.
--
Okay, I found the package at Maven: https://jena.apache.org/download/maven.html
Is this the only way to get it, even if you do not use Maven?
mvnrepository.com is usually a better place to search for a Java package:
If you still want to include JARs by hand (the link above is highlighted), don't forget to manually resolve the JARs that jena-permissions depends on:
P.S. I side with #AndyS that learning a dependency management system is 100% worth the effort.
I found the download link on my own. You need to go here to get the package: https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-permissions/
I have a project where I'd like to use https://www.nuget.org/packages/Bootstrap.Datepicker/, so being a good modern developer I tell VS to add that nuget package. Which is cool. But along with it comes Bootstrap 2.3.1, which I know is a dependency of that package. But my project already has the Bootstrap Less Source (3.2.0.1) package installed, and I'm concerned about having two different "instances" of the "same" package in my project. Another developer on my team has pointed out that any and all Nuget packages that are based on bootstrap probably will require the default one, not the less source package we're using, even though that works best for us.
Is there some way in nuget to tell it to ignore dependencies, or convince it that instead of the dependency it's expecting, it's been met in another way?
I'm in the process of building a javascript plugin that people will be able to install by simply pasting a script tag into their HTML. At times I may wish to include a third-party library in my plugin, but I want to make sure that my plugin will still work if used on a web site that relies on a different version of this same library. Is there a tool I can use to somehow modify the namespace of my required dependencies so that they don't interfere with any other existing scripts or libraries? I have been researching browserify but it's not immediately clear to me from the docs that it can be used to avoid this problem.
everyone.
I am new to Go language and currently I am trying to understand the basics of building Go applications. I met the following problem.
For example, I am using other libraries in my project. I have them locally, on my computer, so my project works fine.
I am loading my code on github and another programmer download it. As I understand, my code won't work, because this programmer doesn't have the libraries I used.
So the question is: What is the best way to share my project with all libraries it has? Should I upload these libraries in the separate repositories? Then to use my project, people need to look inside the code to detect which libraries I am using to download them one by one?
For example, in Java there is such thing like Maven or Ant, which downloads all required dependencies. Is there any tools like this for Go?
Let's call the main file of my project main.go
And I am using my own library: mathutil.go
what is the best way to make this project run on other computers?
Go's dependencies work very much like using Maven or IVY transitive dependencies. When someone does "go get" of your package, anything you depend on will automatically download.
For example, in your source:
import "github.com/foo/bar"
go will automatically download that to your $GOPATH/src/github.com/foo/bar along with your code.
Assuming the third party libs you use are hosted in a public repo (ie: github) then people don't need to do anything.
If the libraries you used are not available on a public repo, you will need to post them somewhere assuming their licensing allows.
Take a look at golang.org/doc/code.html for more details
Version control Best practices.
When developing a program, I use third party libraries, NUnit and others.
I want to share the sources of this program hosted on http://www.codeplex.com/ or http://code.google.com/hosting/.
What are good practices as regards third libraries?
Should I add the dll of my third libraries in the version control ?
Thank you,
With the introduction of NuGet you have a different way to do this.
See this post by David Ebbo: Using NuGet without committing packages.
Basically you use NuGet to download and add package references to the libraries you want (assuming there's NuGet packages for the libraries you need), but do not add the Packages folder to your repository.
Instead you modify your pre-build step of the projects that require packages so that they automatically download the packages required if they're not present.
Testing has shown that this adds a minor delay to the build process when checking if the libraries are present, so this may or may not be good enough for you.
We always do especially if we are linking against a specific version, we have an NUnit folder for example and then a version folder within it.