Skip to content
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.

Add documentation for brew linkapps #22380

Closed
wants to merge 2 commits into from

Conversation

ELLIOTTCABLE
Copy link
Contributor

Although it's in the contribs/ folder, it seems like a rather important command; so I've added documentation for it to the manpage.

Mind you: it's currently documented with the assumption that #22378 and #22379 are accepted as-is, for the most part. I'll be happy to refactor this documentation to reflect whatever decisions are made therein.

@adamv
Copy link
Contributor

adamv commented Sep 9, 2013

Since this command is already referenced in certain caveats, we might as well make it official (and not contrib); which means we can also rename it (once!) at the same time if anyone has a better name for this.

@ELLIOTTCABLE
Copy link
Contributor Author

Any argument against just brew apps?

What about moving it into ln, as brew link --apps? Since that's exactly what it's doing, linking the build-products into a central, generally-accessible directory.

@adamv
Copy link
Contributor

adamv commented Sep 9, 2013

I see the appeal in adding an option to brew link, but don't really want to overload it that way. But would like to hear other maintainers opinions on that.

@adamv
Copy link
Contributor

adamv commented Sep 9, 2013

Also apps works for me so far.

Will also want to add this to the (bash) autocomplete.

@MikeMcQuaid
Copy link
Member

brew apps works for me.

@jacknagel
Copy link
Contributor

Putting my end-user hat on, I wouldn't really expect a command named "apps" to "do stuff" since "apps" is not a verb; it's closer to "uses", "deps", or "outdated". What's wrong with keeping "linkapps" (then nobody has to update scripts or aliases or whatever)?

@ELLIOTTCABLE
Copy link
Contributor Author

I think @adamv is making the point that, if anybody wants to rename it, now is the time. What with it being moved around the source-tree anyway.

My vote is for removing it entirely, in favour of a flag; but that said, I think the sanest route is probably Jack's. That is, not to move it at all.

—

Sent from Mailbox for iPad

On Mon, Sep 9, 2013 at 5:07 PM, Jack Nagel [email protected]
wrote:

Putting my end-user hat on, I wouldn't really expect a command named "apps" to "do stuff" since "apps" is not a verb; it's closer to "uses", "deps", or "outdated". What's wrong with keeping "linkapps" (then nobody has to update scripts or aliases or whatever)?

Reply to this email directly or view it on GitHub:
#22380 (comment)

@adamv
Copy link
Contributor

adamv commented Sep 9, 2013

Keeping the name is fine with me, just throwing the option out there.

@MikeMcQuaid
Copy link
Member

Good points @jacknagel; linkapps is certainly more explicitly obvious.

@adamv
Copy link
Contributor

adamv commented Sep 10, 2013

Merge this documentation change into #22378, since it documents the new (as yet unpulled) behavior.

@adamv
Copy link
Contributor

adamv commented Sep 12, 2013

Closing in favor of #22378.

@adamv adamv closed this Sep 12, 2013
@Homebrew Homebrew locked and limited conversation to collaborators Feb 17, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants