Re: ansible replacement by py-ansible

On 16 Dec 2017, at 01:17, Andrew Fernandes wrote: > Not having the docs is a minus, but supporting py3 is good, so… it’s a wash, > really. How about using pip with git?

Re: ansible replacement by py-ansible

Is it possible to use pip with git? I couldn't find a portfile using, for example, git+https. https://pip.readthedocs.io/en/latest/reference/pip_install/#vcs-support

Re: port "gohome" --> "A keychain cannot be found."

On 2 Jan 2018, at 22:51, Ken Cunningham wrote: > Found a consistent trigger. > If safari is _not_ running: > "port gohome gtk3" -> brings up “A keychain cannot be found” Did you try different versions of Safari? It works fine in v6.

Re: port "gohome" --> "A keychain cannot be found."

On 3 Jan 2018, at 00:24, db wrote: > On 2 Jan 2018, at 22:51, Ken Cunningham > wrote: >> Found a consistent trigger. >> If safari is _not_ running: >> "port gohome gtk3" -> brings up “A keychain cannot be found” > Did you try different versions of Saf

Re: reclaim and rleaves

On 15 Dec 2017, at 15:51, db wrote: > Shouldn't reclaim use rleaves instead of unrequested? As of now I have to > rerun reclaim in order to remove unnecessary ports. Can anyone clarify why multiple runs of reclaim are necessary?

Re: ansible replacement by py-ansible

On 15 Dec 2017, at 15:41, Andrew Fernandes wrote: > Not in the pypi dist! I just checked and manpages, examples, etc are there. https://pypi.python.org/packages/4f/65/ae3ad8589c38f9e04ebc8a824c2880eb4f9e603a1f62b5f5a3f938e524b0/ansible-2.4.2.0.tar.gz#md5=88240a923505d604bd7a4fb91d7721e8

Re: ansible replacement by py-ansible

On 23 Jan 2018, at 11:31, Russell Jones wrote: > Not quite what you're asking, but there is a GitHub portgroup. Yes, I know. I actually tried vcs with pip as the portfile now is, but it didn't work, or at least, I couldn't make it work. But ansible is now pypi-based and imo unnecessarily prepen

Re: Suggestions for hacking sessions & discussions for the MacPorts meeting in March

On 21 Feb 2018, at 17:33, Mojca Miklavec wrote: > - New website! Homebrew/Linuxbrew's are good examples to get up and running quickly, and still have updated technical documentation. > - How to deal with huge number of open tickets on Trac > - It would be fun to go through features of HB an

Re: Search for a MacPorts Mascot: looking for talented artists

On 21 Feb 2018, at 17:32, Mojca Miklavec wrote: > Something in the spirit of ... >http://en.wikifur.com/w/images/4/46/Hexley_fork_450.png I like that MacPorts lacks a mascot identity. But if you really need, want one, then I probably choose Darwin's Hexley. Another that I'd consider, and sin

Re: Suggestions for hacking sessions & discussions for the MacPorts meeting in March

On 22 Feb 2018, at 11:32, Umesh Singla wrote: > On Thu, Feb 22, 2018 at 12:26 AM, db wrote: > On 21 Feb 2018, at 17:33, Mojca Miklavec wrote: > > - New website! > Homebrew/Linuxbrew's are good examples to get up and running quickly, and > still have updated techni

Re: Oh sh!t git

On 22 Feb 2018, at 16:05, Craig Treleaven wrote: > If, like me, you sometimes don’t get git: > http://ohshitgit.com Nomen est omen http://justinhileman.info/article/git-pretty/git-pretty.png http://ndpsoftware.com/git-cheatsheet.html

Re: Search for a MacPorts Mascot: looking for talented artists

On 22 Feb 2018, at 12:24, Mojca Miklavec wrote: > In the spirit of plays around "Port" there's another relevant wikipedia > article: >https://en.wikipedia.org/wiki/Port_wine > But it would not be too tasty to use that given our history with > certain other projects :) :) :) Hexley with a bee

Re: Ports with default modeline & lots of mixed tabs with spaces

On 28 Feb 2018, at 14:58, Ryan Schmidt wrote: > I wouldn't completely change the whitespace of someone else's port, even > after a maintainer timeout. But I would correct whitespace mistakes in > someone else's port after a suitable timeout. Shouldn't port lint be the rule here?

Re: Ports with default modeline & lots of mixed tabs with spaces

On 1 Mar 2018, at 13:14, Ryan Schmidt wrote: > What do you mean? > I don't think port lint currently gives whitespace recommendations. And if it > did, port lint still just provides suggestions that must be moderated by > human decisions. I just tried it and it seems port lint doesn't catch tab

Re: request for port create command, to build a portfile from a URL

On 6 Mar 2018, at 16:19, Joshua Root wrote: > On 2018-3-7 01:58 , Ken Cunningham wrote: >> >> port create URL >> Might make things faster and easier for people to get started and up and >> running. > There's a fairly basic tool called portfile-gen in contrib. I took a bit to find it, so here's

Re: request for port create command, to build a portfile from a URL

On 7 Mar 2018, at 01:53, Rainer Müller wrote: > On 2018-03-06 23:00, db wrote: >> [...] an *overview* of how to write a portfile is much needed. > Isn't this what this chapter in the guide is supposed to provide? > https://guide.macports.org/#development Yes, supposed.

Re: Changing default cxx_stdlib to libc++

On 9 Mar 2018, at 01:27, Ryan Schmidt wrote: > When would we run this script to delete libstdc++ archives? Presumably, after > all legacy users have MacPorts 2.5 and have switched to libc++. How about those that build MP from source?

Re: Changing default cxx_stdlib to libc++

On 9 Mar 2018, at 15:21, Joshua Root wrote: > On 2018-3-9 20:38 , db wrote: >> On 9 Mar 2018, at 01:27, Ryan Schmidt wrote: >>> When would we run this script to delete libstdc++ archives? Presumably, >>> after all legacy users have MacPorts 2.5 and have switched to

Re: Changing default cxx_stdlib to libc++

On 10 Mar 2018, at 00:09, Joshua Root wrote: > On 2018-3-10 08:43 , db wrote: >> >> If I build base and ports from source, will buildfromsource be changed >> unilaterally by MP or would it need user intervention? I also have certain >> versions of gcc and llvm locall

Re: Changing default cxx_stdlib to libc++

On 10 Mar 2018, at 18:06, "Kenneth F. Cunningham" wrote: > I think I"m likely not going to change anything on my LibcxxOnOlderSystems > 10.6.8 system for a while, db. It will continue to work just as it does now, > and I don't mind building from source -- kind

Re: Changing default cxx_stdlib to libc++

On 11 Mar 2018, at 02:47, "Kenneth F. Cunningham" wrote: > On 2018-03-10, at 12:23 PM, db wrote: >> Except for building from source for minor versions and revbumps, especially >> large binaries, and for ports that have open defects. Oh well… > Well, everything for

Re: Python default version

On 12 Mar 2018, at 15:46, Ryan Schmidt wrote: > Should we change the default python version to 3.6 now, or soon? Soon. Btw, https://brew.sh/2018/01/19/homebrew-1.5.0/ (first bullet).

Re: Changing default cxx_stdlib to libc++

On 11 Mar 2018, at 15:47, Ken Cunningham wrote: >> On Mar 11, 2018, at 06:06, db wrote: >> On 11 Mar 2018, at 02:47, "Kenneth F. Cunningham" >> wrote: >>>> On 2018-03-10, at 12:23 PM, db wrote: >>>> Except for building from source for

Re: Changing default cxx_stdlib to libc++

On 12 Mar 2018, at 21:56, Ryan Schmidt wrote: > I'm not aware of any plan to notify users of the cxx_stdlib change, other > than the same way that users are notified of any other port update being > available: by the user running "sudo port selfupdate" and then examining the > output of "port o

Re: Changing default cxx_stdlib to libc++

On 12 Mar 2018, at 21:35, Ryan Schmidt wrote: > On Mar 12, 2018, at 13:56, db wrote: >> If not, shouldn't it, prior to accepting an updated port definition? > The buildbot is only engaged after a commit is in the repository master > branch. > We have a separate system, usi

Re: Changing default cxx_stdlib to libc++

On 13 Mar 2018, at 15:22, Ryan Schmidt wrote: > On Mar 13, 2018, at 08:47, db wrote: >> On 12 Mar 2018, at 21:35, Ryan Schmidt wrote: >>> On Mar 12, 2018, at 13:56, db wrote: >>>> If not, shouldn't it, prior to accepting an updated port definition? >>>

Re: Changing default cxx_stdlib to libc++

On 13 Mar 2018, at 17:10, Mojca Miklavec wrote: > The main problem is that Travis is *not* out main build system, we use > a different system for that. Travis has lots of limitations: Got it. Then why use it in the first place instead of an alternative CI?

Re: Changing default cxx_stdlib to libc++

On 14 Mar 2018, at 00:22, Mojca Miklavec wrote: > Because someone would need to write the code for an alternative CI Wouldn't self-hosted GitLab CI be good enough? I get the impression that testing across the board is not a priority.

Re: Changing default cxx_stdlib to libc++

On 14 Mar 2018, at 01:14, Rainer Müller wrote: > Are you going to sponsor a dedicated Mac server for GitLab CI? > Travis CI is available at no cost and we have no funds to pay for anything. If MacPorts is short on resources, these could be listed on the website. Folks can certainly ask around.

Re: CI system for PR builds (was: Re: Changing default cxx_stdlib to libc++)

On 14 Mar 2018, at 04:08, Ryan Schmidt wrote: > I was not aware of the existence of GitLab CI, but I haven't done a survey of > CI systems, mainly because we already selected one many years ago: Buildbot. GitLab CI is now integrated in GitLab, but AFAIK doesn't integrate with GitHub right now u

Re: CI system for PR builds (was: Re: Changing default cxx_stdlib to libc++)

> On Mar 14, 2018, at 07:25, db wrote: >> Otherwise, you could make the machines sync to the packages public server >> for the distributable, and to a private server for the non-distributable >> binaries. > I can't find an interpretation of that sentence that helps to

Re: Changing default cxx_stdlib to libc++

On 15 Mar 2018, at 05:19, Ryan Schmidt wrote: > On Mar 14, 2018, at 07:23, db wrote: >> On 14 Mar 2018, at 01:14, Rainer Müller wrote: >>> Are you going to sponsor a dedicated Mac server for GitLab CI? >>> Travis CI is available at no cost and we have no funds to pay f

Re: MacPorts from behind proxy servers & fetching the file directly

On 16 Mar 2018, at 12:31, Mojca Miklavec wrote: > While discussing GSOC with Umesh, he repeated what we already > discussed during the meeting. Students in campuses (including the one > where he is studying and from which roughly 40 students participate in > GSOC each year) might be behind proxies

Re: MacPorts from behind proxy servers & fetching the file directly

On 16 Mar 2018, at 16:03, "Daniel J. Luke" wrote: > portfiles could in theory attempt to connect to any port, so a comprehensive > list like you're asking for is probably not possible to create. But there could be one in practice, as there is infrastructure building all ports. Ever upgraded out

Re: How to prevent fetching from macports mirrors

On 19 Mar 2018, at 17:42, Rainer Müller wrote: > With git master: > $ sudo port fetch --no-mirrors > With 2.4.x: > $ sudo port fetch global_mirror_site= Is there any way to set in macports.conf to only fetch from master site and/or, if needed, try a mirror?

Re: Enhance livecheck to check not only version but also checksums

On 20 Mar 2018, at 00:59, Ryan Schmidt wrote: > Once that's done, it makes it easier to implement a better "bump" command -- > one that can use any published checksums and compute the rest, and warn if no > checksums were published. > https://trac.macports.org/ticket/53851 Sorry, this one is of

Re: How to prevent fetching from macports mirrors

On 20 Mar 2018, at 03:34, Ryan Schmidt wrote: > On Mar 19, 2018, at 16:29, db wrote: >> Is there any way to set in macports.conf to only fetch from master site >> and/or, if needed, try a mirror? > What do you mean? MacPorts already tries to fetch from the master_sites

Re: Enhance livecheck to check not only version but also checksums

On 20 Mar 2018, at 14:54, Rainer Müller wrote: > https://lists.macports.org/pipermail/macports-announce/ > https://github.com/macports/macports-base/blob/master/ChangeLog macports-announce seems scant to me. I suggest using a GitHub issue, like Linuxbrew does, https://github.com/Linuxbrew/brew/i

Re: How to prevent fetching from macports mirrors

On 20 Mar 2018, at 14:40, Joshua Root wrote: > host_blacklist, preferred_hosts > How do you blacklist MP mirrors? Like so: host_blacklist *.packages.macports.org ?

Re: How we announce MacPorts changes (was: Re: Enhance livecheck to check not only version but also checksums)

On 21 Mar 2018, at 00:31, Ryan Schmidt wrote: > On Mar 20, 2018, at 09:20, db wrote: >> macports-announce seems scant to me. > Intentionally. We only post there when we have something to announce, which > is seldom. I still think things like python default and protobuff changes,

Re: How we announce MacPorts changes

On 21 Mar 2018, at 12:49, Rainer Müller wrote: > Apparently you care a lot about these details. As you are already actively > following the mailing lists and commit logs, feel free to prepare a weekly > newsletter of the important changes to the ports tree. I'd rather follow irregular updates (

Re: How we announce MacPorts changes

On 21 Mar 2018, at 14:00, Rainer Müller wrote: > On 2018-03-21 13:12, db wrote: >> >> I'd rather follow irregular updates (see linuxbrew updates issue on GH) and >> check first updated technical documentation, > At this point I really do not know what to make o

Re: How to prevent fetching from macports mirrors

On 21 Mar 2018, at 00:54, Ryan Schmidt wrote: > On Mar 20, 2018, at 09:21, db wrote: >> How do you blacklist MP mirrors? Like so: host_blacklist >> *.packages.macports.org ? > I don't think it supports wildcards. List each complete hostname you want to > blacklist.

Re: How to prevent fetching from macports mirrors

On 21 Mar 2018, at 23:04, Ryan Schmidt wrote: > List only the hostnames, not full URLs. My bad. This works: host_blacklist distfiles.macports.org aarnet.au.distfiles.macports.org ywg.ca.distfiles.macports.org ykf.ca.distfiles.macports.org pek.cn.distfiles.macports.org lil.fr.distfiles

<    1   2