package-managers

I want to make an application that could send itself (apk file) by bluetooth. but i have trouble with finding the apk file path. i tried this code: final PackageManager pm = this.getPackageManager(); List<PackageInfo> packages = pm.getInstalledPackages(PackageManager.GET_META_DATA); String st = null; for (PackageInfo packageInfo : packages) { if(packageInfo.packageName.contains("testbutton")) st=packageInfo.packageName; } Intent intent = new Intent(); intent.setAction(Intent.ACTION_SEND); intent.setType("image/*"); String uri = "/data/app/"; uri+=st; intent.putExtra(Intent.EXTRA_STREAM, Uri

In composer.json I've got { "require": { "phpdocumentor/phpdocumentor": "*" } } It's what is there because I'm trying to install phpDocumentor into an isolated folder with ./composer.phar install command. But what I'm getting is Loading composer repositories with package information Updating dependencies (including require-dev) Your requirements could not be resolved to an installable set of packages. Problem 1 - phpdocumentor/phpdocumentor v2.0.0 requires phpdocumentor/template-abstract ~1.2 -> satisfiable by phpdocumentor/template-abstract[1.2, 1.2.1]. - phpdocumentor/phpdocumentor v2.0.1

I don't really understand what is happening and maybe you can give me an idea. I use getInstalledPackages() in order to get a list of all user installed applications and their permissions. Here is how I do it: private PackageManager pm; @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); pm = getPackageManager(); getListData(); } private void getListData() { backTask = new BackTask(); backTask.execute(); } protected class BackTask extends AsyncTask<Context, String, ArrayList<App>> { .... @Override protected ArrayList<App> doInBackground(Context...

I am trying to manage my node package dependencies. I'd like to be able to install all the required dependencies by running a command, and from what I have read, one way to achieve this is using a package.json file and running npm install . So my JSON file looks like this: { "name": "Name-Of-The-Thing", "description": "The Thing's Name", "author": "The Dude <the.dude@dudethinking.com>", "dependencies": { "mocha":">= 1.12.0", "mocha-phantomjs":">= 3.1.0", "chai":">= 1.7.2", "phantomjs":">= 1.9.1" } } However npm install reports the following error: npm ERR! Failed to parse json npm ERR!

I know Package Manager like NuGet help us when we want to use third party components. From Nuget Codeplex Page: NuGet is a free, open source developer focused package management system for the .NET platform intent on simplifying the process of incorporating third party libraries into a .NET application during development. There are a large number of useful 3rd party open source libraries out there for the .NET platform, but for those not familiar with the OSS ecosystem, it can be a pain to pull these libraries into a project. Let’s take ELMAH as an example. It’s a fine error logging utility

I'm trying to figure out what the best way to handle this scenario is. Let's say I have a library that's referenced by multiple different non-related solutions, let's call it WebServiceInterface.dll. This library has a dependency on JSON.NET. Before NuGet The JSON.NET binary was referenced via a SVN external in the WebServiceInterface project. Other solutions which had a dependency on WebServiceInterface referenced the project (also as an SVN external) and as a result pulled both the project, and it's dependencies. With NuGet I haven't figured out how to force the JSON.NET reference to be

I'm trying to understand this part: http://getcomposer.org/doc/02-libraries.md#lock-file this lock file will not have any effect on other projects that depend on it. It only has an effect on the main project" Does that mean that if project P depends on library A, and library A depends on library B v1.3, project P won't care about the version of library B, and will possibly install B 1.4 instead? What's the point then? Or does it mean the opposite, as one would expect from a dependency manager? naderman Composer dependencies are defined in composer.json . When running composer install for the

I have a standard homebrew install inside of usr/local/ When I try: Larson-2:~ larson$ brew install postgresql Error: Cannot write to /usr/local/Cellar And when I use sudo: Larson-2:~ larson$ sudo brew install postgresql Cowardly refusing to `sudo brew install' What am I doing wrong? You somehow have limited permissions to /usr/local/Cellar . Brew doesn't like to install with sudo which is why it refuses. Check the permissions: ls -ld /usr/local/Cellar Open them up for writing: sudo chmod a+w /usr/local/Cellar Do not use sudo when working with brew (for security reasons). You've to simple set