Some good ideas there - sounds like we have the makings of an update
to that wiki page happening. This looks workable.
Might be nice someday to have this as a few simple commands, like
homebrew's "peg" and "unpeg" commands.
a command to list a port's history doing all that git stuff mentioned
in
On 2016-12-29 11:53 , Fred Wright wrote:
On Mon, 26 Dec 2016, Ken Cunningham wrote:
That gives you the full history of macports-ports back in time. Then use
port info PORT
to find the path to your port, eg in this example case devel/libuv
It's unfortunate that there isn't a command to giv
On Mon, 26 Dec 2016, Ken Cunningham wrote:
> So, this turns out to be a lot easier than I originally thought it
> would be, and probably is no more difficult than svn was. This may not
> be the most efficient way of doing it, but it's fairly easy to
> understand, and it works for me.
>
> Here are
On Thu, 29 Dec 2016, [windows-1252] Marko Käning wrote:
> On 29 Dec 2016, at 00:05 , Mojca Miklavec wrote:
[...]
> > Today I'm exercising a somewhat weird practice. I collect just a small
> > number of symlinks to macports-ports from git in my local tree. I'm
> > not too happy about this though,
On 29 Dec 2016, at 00:05 , Mojca Miklavec wrote:
> On 28 December 2016 at 23:59, Marko Käning wrote:
>> On 28 Dec 2016, at 23:18 , Marko Käning wrote:
>>
>>> This way I shouldn’t get any shadowing…
>>
>> Ha, and I wouldn’t see any updates of my local source either.
>
> Exactly.
>> So, no, I
On 28 December 2016 at 23:59, Marko Käning wrote:
> On 28 Dec 2016, at 23:18 , Marko Käning wrote:
>
>> This way I shouldn’t get any shadowing…
>
> Ha, and I wouldn’t see any updates of my local source either.
Exactly.
But one of the questions arises: why do you need the global index at all?
> S
On 28 Dec 2016, at 23:18 , Marko Käning wrote:
> This way I shouldn’t get any shadowing…
Ha, and I wouldn’t see any updates of my local source either.
So, no, I have to have my local port sources in front of the default rsync’ed
source,
if I am not completely mistaken. Shadowing is unavoidab
On 28 Dec 2016, at 23:10 , Mojca Miklavec wrote:
> Just your local copy shadowing everything else in the global portindex.
Jesus, I thought that the rsync tree would still be taken as the most
up-to-date one.
OK, that means I’d have to move my local tree behind the rync’ed one, right?
This w
Dear Marko,
On 28 December 2016 at 22:31, Marko Käning wrote:
> Hi,
>
> just now I ran a selfupdate and didn’t get notified of any outdated ports:
> ---
> $ sudo port selfupdate && port outdated
> Password:
> ---> Updating MacPorts base sources using rsync
> MacPorts base version 2.3.5 installed,
On 28 Dec 2016, at 22:31 , Marko Käning wrote:
> What am I missing here? Or is MacPorts’ portindexing indeed not working
> ATM!!!???
... and, if it is indeed working - as to be expected - could my observations be
linked to the fact that I have a local port directory with its own Portindex*
fil
Hi,
just now I ran a selfupdate and didn’t get notified of any outdated ports:
---
$ sudo port selfupdate && port outdated
Password:
---> Updating MacPorts base sources using rsync
MacPorts base version 2.3.5 installed,
MacPorts base version 2.3.5 downloaded.
---> Updating the ports tree
---> M
11 matches
Mail list logo
