Automattic / Automattic/cloudup-cli

Homebrew complains about `up-config`

Open
#46 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
84
Forks
14
PR merge metrics
No merged PRs in 30d

Description

I have node/npm installed via [homebrew](http://brew.sh) on a Mac as well as `up(1)`.

When I run `brew doctor` to ensure that things are silky smooth, it complains:

```
Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:

/usr/local/share/npm/bin/up-config
```

Be nice to use a different filename if possible.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the `up-config` entry point in the cloudup-cli package and how it is installed under `/usr/local/share/npm/bin/`. Determine whether the executable can use a different filename, then verify that `brew doctor` no longer reports the installed script.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.