Create a homebrew port of awesome.
That way, not only will you get what you wanted,
but everyone will benefit from the fruits of your labor.
... or take the more enlightened route and switch to using exclusively
MacPorts ;) Is there anything Homebrew has than MP doesn't ?
:) Not much, if any. But the reverse is constantly true. LaTeX is the one
that got me to convert people in the CS department.
—Mark
___
Mark E. Anderson e...@emer.net
On Fri, Aug 9, 2013 at 7:08 AM, Chris Jones jon...@hep.phy.cam.ac.ukwrote:
Create a homebrew port of
Please enlighten, convert people to what and why?
Regards,
Bradley Giesbrecht (pixilla)
On Aug 9, 2013, at 6:32 AM, Mark Anderson wrote:
:) Not much, if any. But the reverse is constantly true. LaTeX is the one
that got me to convert people in the CS department.
—Mark
He converted people to MacPorts because we have what Homebrew does not (that,
and, you know, being a package manager).
Please enlighten, convert people to what and why?
:) Not much, if any. But the reverse is constantly true. LaTeX is the one
that got me to convert people in the CS
On Jul 04 09:44:06, rai...@krugs.de wrote:
Hi
I am using homebrew at the moment, but there are certain packges, which
are not on homebrew (e.g. awesome and kde apps).
Create a homebrew port of awesome.
That way, not only will you get what you wanted,
but everyone will benefit from the
On Jul 5, 2013, at 5:22 PM, Brandon Allbery allber...@gmail.com wrote:
$PATH is only one of the possible problems. Does homebrew prevent promiscuous
configure scripts from scanning /sw, /opt/local, etc. for libraries?
If GNU's Autotools were really functional in practice, we wouldn't need
On Jul 4, 2013, at 02:44, Rainer M Krug wrote:
This would then mean, that two package managers can co-exist, or only
that macports can work reliably with homebrew installed, but not the
other way round?
With the latest Homebrew 0.9.3 it’s quite the contrary. Thanks
to the new “Superenv”,
On Fri, Jul 5, 2013 at 11:12 AM, Guido Soranzio guido.soran...@gmail.comwrote:
On Jul 4, 2013, at 02:44, Rainer M Krug wrote:
This would then mean, that two package managers can co-exist, or only
that macports can work reliably with homebrew installed, but not the
other way round?
With
With the latest Homebrew 0.9.3 it’s quite the contrary. Thanks
to the new “Superenv”, the user’s PATH is ignored completely:
https://github.com/mxcl/homebrew/wiki/Homebrew-0.9.3.
Pardon me if I'm slightly amused by what they've done. Homebrew (in
contrast to MP) is all about using what's
Hi
I am using homebrew at the moment, but there are certain packges, which
are not on homebrew (e.g. awesome and kde apps).
Therefore I am thinking abiout using these two package managers in
parallel.
I know this *can* cause problems, but is it likely to cause problems?
What do I have to be
On Thu, Jul 4, 2013 at 9:44 AM, Rainer M Krug wrote:
Hi
I am using homebrew at the moment, but there are certain packges, which
are not on homebrew (e.g. awesome and kde apps).
Therefore I am thinking abiout using these two package managers in
parallel.
I know this *can* cause problems,
Mojca Miklavec mojca.miklavec.li...@gmail.com writes:
On Thu, Jul 4, 2013 at 9:44 AM, Rainer M Krug wrote:
Hi
I am using homebrew at the moment, but there are certain packges, which
are not on homebrew (e.g. awesome and kde apps).
Therefore I am thinking abiout using these two package
Hi,
On Thu, Jul 04, 2013 at 09:44:06AM +0200, Rainer M Krug wrote:
Therefore I am thinking abiout using these two package managers in
parallel.
I know this *can* cause problems, but is it likely to cause problems?
What do I have to be aware about? Any experiences?
Unfortunately it is
Clemens Lang c...@macports.org writes:
Hi,
On Thu, Jul 04, 2013 at 09:44:06AM +0200, Rainer M Krug wrote:
Therefore I am thinking abiout using these two package managers in
parallel.
I know this *can* cause problems, but is it likely to cause problems?
What do I have to be aware about?
On Thu, Jul 4, 2013 at 10:27 AM, Rainer M Krug wrote:
Mojca Miklavec writes:
I thought along the same lines - but I am thinking of trying to use
awesome windows manager (macports only) and at the same time I am using
offlineimap and notmuch which are installed via homebrew - so this wont
Mojca Miklavec mojca.miklavec.li...@gmail.com writes:
On Thu, Jul 4, 2013 at 10:27 AM, Rainer M Krug wrote:
Mojca Miklavec writes:
I thought along the same lines - but I am thinking of trying to use
awesome windows manager (macports only) and at the same time I am using
offlineimap and
On Jul 4, 2013, at 02:44, Rainer M Krug wrote:
I am using homebrew at the moment, but there are certain packges, which
are not on homebrew (e.g. awesome and kde apps).
Therefore I am thinking abiout using these two package managers in
parallel.
I know this *can* cause problems, but is
Great job! Thanks!
On 4 Jul 2013, at 11:07, Clemens Lang wrote:
I am working on a mechanism built into port to prevent problems with
homebrew or fink co-installed on the same machine
--
Eneko Gotzon Ares
___
macports-users mailing list
18 matches
Mail list logo
