Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add Hyperspaces #8010

Closed
wants to merge 1 commit into from
Closed

add Hyperspaces #8010

wants to merge 1 commit into from

Conversation

bashu
Copy link
Contributor

@bashu bashu commented Dec 11, 2014

No description provided.

@tapeinosyne
Copy link
Contributor

Hello @bashu, and thanks for adding a new cask. Given that the application is abandoned and only works on fairly old OS X versions, I would like to ask for the opinion of other maintainers before merging.

@caskroom/maintainers, considering that we now have depends_on :macos, how do we feel about Casks which only work on OS X releases we do not officially support?

@rolandwalker
Copy link
Contributor

There's a policy for that: Software in the main repo should run on the latest release of OS X or the previous point release.

Other Casks are welcome, but should live in the versions repo. Note that text at the link above is partly outdated; I have updated it already in a private branch.

(Hi @bashu !)

@jimbojsb
Copy link
Contributor

Wow that's an ancient piece of software. I see no reason to add it if the maximum it supports its 10.6.

Sent from my iPhone

On Dec 11, 2014, at 7:53 AM, ndr [email protected] wrote:

Hello @bashu, and thanks for adding a new cask. Given that the application is abandoned and only works on fairly old OS X versions, I would like to ask for the opinion of other maintainers before merging.

@caskroom/maintainers, considering that we now support depends_on :macos, how do we feel about Casks which work only on OS X releases older than the ones we officially support?


Reply to this email directly or view it on GitHub.

@tapeinosyne
Copy link
Contributor

There's a policy for that: Software in the main repo should run on the latest release of OS X or the previous point release.

The policy was set before the introduction of an OS X dependency stanza, which leads me to wonder if someone feels inclined to revisit it. So far, we all agree that it is best to use caskroom/versions; the next maintainer who agrees should feel free to close the PR and move the Cask to our versions repository.

@tapeinosyne tapeinosyne mentioned this pull request Dec 11, 2014
@vitorgalvao
Copy link
Member

Wow that's an ancient piece of software. I see no reason to add it if the maximum it supports its 10.6.

I agree. Searching issues, there doesn’t even seem to have ever been any demand for it. This cask, I predict, will remain untouched (including on the user’s side) until the developer takes the page down and we remove the cask on account of the software no longer being available. To add it anywhere, I’d add it directly to the boneyard.

@rolandwalker
Copy link
Contributor

We are opening orthogonal discussion threads:

@ndr-qef is pointing out that the new depends_on :macos form could mean it is practical to let some stuff from the versions repo live in the main, which might be a usability improvement. @vitorgalvao is pointing out that 10.6 is older than what we usually deal with, raising maintainability concerns. I am finding problems with the current doc.

I'd like to invoke the Subjectivity Rule. The docs say that this Cask goes to versions, though it is only halfway explicit.

If we say the rule is "older but not too old" we will trip over each other trying to apply it. Let's send this Cask to versions per the docs (closing this PR) and open separate issues WRT changing the docs.

@bashu your contributions are awesome.

@bashu bashu deleted the hyperspaces branch December 15, 2014 12:12
@Homebrew Homebrew locked and limited conversation to collaborators May 8, 2018
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.

5 participants