Conversation
|
||
depends_on :gpg | ||
depends_on "curl" | ||
depends_on "gtk+" if build.with? "gui" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use => :optional
here instead, thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do I translate the :optional/:recommended over to the build option of using lablgtk or not ?
Should the GUI just be made mandatory, so that there is no way to install CLI only (skip gtk+)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The option will be named without-gtk+
instead. It should also probably default to off.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I default it to off, it won't be in the bottle ? That was the main reason for leaving it on.
In other distributions, the GUI goes in a separate package: "0install" vs. "0install-core"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeh, we default to more minimal versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is unfortunate (no gui bottle), since gtk+ is one of the more annoying ones.
But at least you can install that + deps (and ocaml/opam + boost) from bottles...
Maybe worth just having the non-head build in the formula first? Looks like the head build is quite a bit more complicated? |
Actually it is the non-head build that is complicated, due to the want of using resources...
But that doesn't yield us any bottles, which means that users need to install ocaml/opam. Resources need to be versioned, however, so then it doesn't work with a HEAD build ? |
Resources could potentially be unversioned Git repositories if they are only in the |
@MikeMcQuaid: the resources are all in the same repository, but I suppose that could be done too... |
url "https://opam.ocaml.org/archives/lablgtk.2.18.3+opam.tar.gz" | ||
version "2.18.3" | ||
sha256 "f0b7ed0bd85f6cf4b4c5f81966f03763e76bb9f866f5172511ce48cf31fd433c" | ||
end if build.with? "gtk+" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be:
if build.with? "gtk"
resource "lablgtk" do
url "https://opam.ocaml.org/archives/lablgtk.2.18.3+opam.tar.gz"
version "2.18.3"
sha256 "f0b7ed0bd85f6cf4b4c5f81966f03763e76bb9f866f5172511ce48cf31fd433c"
end
end
The end if
lines are confusing and we've been trying to wipe them out for a while.
Hope this isn't another one of those nit-pickings where just it ends up lying around in the end, like #28771 |
Referencing a PR that was some 15000 Issues/PRs back isn't terribly helpful. Maintainers want things to be as expected before going in otherwise at some point we end up having to fix them. If it meets maintainer's concerns & our minimum addition requirements, it will be merged. As far as I can see, there's not much left to deal with before this is fine. Three nits, and we should be golden. |
sha256 "12de771be748bce9350c90bc4720029a566b078ceabd335af09386ac6a37df2b" | ||
|
||
depends_on :gpg | ||
depends_on "curl" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it incapable of using the system curl
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, it should be "new enough". Dropping the curl then...
@DomT4: ok, thanks. seems like a missed one new dep-of-a-dep, and put the archives in the wrong place... |
@DomT4: seems like it doesn't download the resources on just brew install (not sure when, "fetch" ?) |
i.e. the :build doesn't work, because it only adds "gtk+" to the path but not "pango" and "glib" etc etc. |
ah, normally the |
Funky. As long as it works, I'm happy to revert to the |
It was pointed out to me that build deps having broken pkg-config is a feature: #41759 |
As long as it works optionally that's fine. We very rarely build GUIs by default anyhow. Sent from my iPhone
|
|
||
def install | ||
# Parallel builds fail for some of these opam libs. | ||
ENV.deparallelize |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you report issues upstream for these? Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do (as soon as I remember which of the modules it was that failed)
Hmm, build worked fine without it. Maybe the -j1
caution got outdated.
What else needs to happen for this to get merged? |
Thanks for your contribution to Homebrew! Without people like you submitting PRs we couldn't run this project. You rock! |
Another attempt, after the previous formula had several issues. Hopefully this is better...