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
Hi
I am looking for an easy way of installing the development version
(HEAD) of grass.
under homebrew, I can simply say
,
| brew install grass --HEAD
`
to instal the development version instead of the stable one - is there
something similar in port?
Thanks,
Rainer
--
Rainer M.
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 10:08:01AM +0200, Rainer M Krug wrote:
I am looking for an easy way of installing the development version
(HEAD) of grass.
under homebrew, I can simply say
,
| brew install grass --HEAD
`
to instal the development version instead of the stable one
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 10:08:01AM +0200, Rainer M Krug wrote:
I am looking for an easy way of installing the development version
(HEAD) of grass.
under homebrew, I can simply say
,
| brew install grass --HEAD
`
to instal the
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 04, 2013 at 11:10:33AM +0200, Rainer M Krug wrote:
So then I would have to install grass as usual via
,
| port install grass
`
Yes.
and then upgrade it and specify to use HEAD to fetch - how can I do
this?
MacPorts has no way to do this from the command line like
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
Clemens Lang c...@macports.org writes:
On Thu, Jul 04, 2013 at 11:10:33AM +0200, Rainer M Krug wrote:
So then I would have to install grass as usual via
,
| port install grass
`
Yes.
and then upgrade it and specify to use HEAD to fetch - how can I do
this?
MacPorts has no way
Well, the answer lies in this command:
$ portrdeps percona-toolkit
The following ports are dependencies of percona-toolkit @2.1.5_0+perl5_16:
p5.16-time-hires
perl5.16
gdbm
gettext
expat
libiconv
gperf
ncurses
p5.16-dbd-mysql
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
On Jul 4, 2013, at 07:32, Enrico Placci wrote:
I hope my email does not sound too whiney, my intention is to give
constructive feedback, hopefully my frustration won't overshadow that.
I'm writing you from a burning laptop, where macports decided to be too smart
and did what it thought I
On 2013-07-04, at 13:44, Aljaž Srebrnič wrote:
So, I either suggest running sudo port -cn upgrade percona-toolkit, or
defining an alias like alias sp=sudo port -cn and using that.
I hope this helps,
Aljaž
Thank you , it helps! I totally missed that.
On 2013-07-04, at 13:57, Ryan
Because they are direct or indirect dependencies of the port you asked to
install or upgrade.
But there is really no need to upgrade them, they already satisfy the
dependency. This wasn't even too bad, after all, when I hit gtk I want to cry.
oh but there is a need to upgrade all
On Jul 4, 2013, at 08:39, Enrico Placci wrote:
On 2013-07-04, at 13:57, Ryan Schmidt wrote:
On Jul 4, 2013, at 07:32, Enrico Placci wrote:
So why would I want to upgrade
ncurses @5.9_1 to @5.9_2
gettext @0.18.2_1 to @0.18.2.1_0
perl @5.12.4_1+dtrace to @5.12.4_2+dtrace
zlib @1.2.7_0
On Jul 4, 2013, at 09:01, Rainer Müller wrote:
I want to share an unobvious feature
of bash with you that helps in situations like this. Quoting the man page:
If the last character of the alias value is a blank, then the next
command word following the alias is also checked for alias
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
20 matches
Mail list logo
