ungoogled-chromium - Google Chromium, sans integration with Google

Hi I filed a request for this port. I post to the list because I think ungoogled-chromium is noteworthy, regardless if someone tries to make a port for it. https://github.com/Eloston/ungoogled-chromium https://trac.macports.org/ticket/62505

GSoC 2019

On 2 Apr 2019, at 17:11, macports-dev-requ...@lists.macports.org wrote: > GSoC 2019 Could it be possible to relocate all this topics somewhere else?

New website design

On 6 Feb 2019, at 13:00, macports-dev-requ...@lists.macports.org wrote: > Message: 2 > Date: Tue, 5 Feb 2019 21:31:22 +0100 > From: Mojca Miklavec > To: MacPorts Development > Subject: New website design > Message-ID: > > Content-Type: text/plain; charset="UTF-8" > Our website design is i

Re: macports rot

On 16 Dec 2018, at 13:00, macports-dev-requ...@lists.macports.org wrote: > Message: 1 > Date: Sat, 15 Dec 2018 13:48:21 +0100 > From: Nils Breunese > > I’m also not involved in most upstream projects for the ports I maintain, but > especially when the upstream project has a website project you c

Re: CI system for PR builds

On 12 Apr 2018, at 20:16, Ryan Schmidt wrote: > You may have noticed that discussion about the issue resumed 4 weeks ago, and > a milestone was assigned. I didn't notice the milestone. Is 2.6 next year's?

Re: How to submit changes with a GitHub Pull Request (was Re: CI system for PR builds)

On 12 Apr 2018, at 19:52, Craig Treleaven wrote: > Is there a playground somewhere to try out such features? For those of us > that are somewhat git- and github-challenged. Not that I'm aware of. Just fork some repo or create a new one and make it your playground.

Re: CI system for PR builds

On 12 Apr 2018, at 18:52, Ryan Schmidt wrote: > 1. MacPorts does not have a method of declaring that a port does not build on > a version of macOS. Such a feature is being discussed: > https://trac.macports.org/ticket/15712 > In the absence of this feature, we write pre-fetch blocks that manually

Re: How to submit changes with a GitHub Pull Request (was Re: CI system for PR builds)

On 12 Apr 2018, at 14:27, Mojca Miklavec wrote: > What nobody mentioned so far is that one can also simply click "Edit" on the > existing Portfile on GitHub interface and that will also open a pull request. Interesting. It seems that 'Create new file' would have a similar effect. 'Upload files'

Re: CI system for PR builds

On 8 Apr 2018, at 02:04, Rainer Müller wrote: > So here is the full plan in detail: Side note: Wouldn't it be feasible to adjust portfiles based on CI's feedback? Let's say, you have something build on 10.6-10.13, but for whatever reason it fails on 10.9, so that could be reflected in the portf

Re: How to submit changes with a GitHub Pull Request (was Re: CI system for PR builds)

On 11 Apr 2018, at 19:24, Perry E. Metzger wrote: > The main steps are: > […] > [By the way, if someone wants to turn this email into a document, I > was pretty careful writing what's above so that would be easy.] Thanks for the write-up. Although I probably rather prefer the PR way, it's gettin

Re: CI system for PR builds

On 11 Apr 2018, at 15:44, Mojca Miklavec wrote: > On 11 April 2018 at 14:11, db wrote: >> On 10 Apr 2018, at 20:07, Mojca Miklavec wrote: >>> >>>> That streamlined process is what keeps new and updated portfiles in my >>>> local repo… >>> I h

Re: CI system for PR builds

On 10 Apr 2018, at 20:07, Mojca Miklavec wrote: > On 7 April 2018 at 15:45, db wrote: >> On 7 Apr 2018, at 14:37, Ryan Schmidt wrote: >> Is buildbot running on your basement??? > Yes (not mine). > […] >> Testing and reproducibility, doesn't seem to me as user to be

Re: CI system for PR builds

On 8 Apr 2018, at 13:50, Ryan Schmidt wrote: > On Apr 8, 2018, at 06:49, db wrote: > On 8 Apr 2018, at 13:34, Ryan Schmidt wrote: >>> No, as I think we've explained several times already, now, Travis CI builds >>> the proposed change automatically, immediat

Re: CI system for PR builds

On 8 Apr 2018, at 13:34, Ryan Schmidt wrote: > No, as I think we've explained several times already, now, Travis CI builds > the proposed change automatically, immediately after it's submitted. The > purpose is to verify that it builds, and the results of that build can inform > our review. Th

Re: CI system for PR builds

On 8 Apr 2018, at 13:18, Ryan Schmidt wrote: > On Apr 8, 2018, at 06:12, db wrote: >> That seems to waste at least buildtime and storage. > What do you mean? >> Many updates and revbumps could be almost automatically deployed (after a >> quick review). > Isn't

Re: CI system for PR builds

On 8 Apr 2018, at 12:42, Zero King wrote: > On Sun, Apr 08, 2018 at 12:20:34PM +0200, db wrote: >> If you review the code before, that should never be the case and it would >> build just once if it succeeds, right? Or am I missing something how PRs are >> handled? > CI

Re: CI system for PR builds

On 7 Apr 2018, at 19:44, Clemens Lang wrote: > Remember that Portfiles can execute arbitrary code and root access is > available from Portfiles. We do not want to run arbitrary code in a PR > on the same build machines we use to build packages that we will > distribute to our users. A malicous att

Re: CI system for PR builds

Thanks for the explanation. On 7 Apr 2018, at 14:37, Ryan Schmidt wrote: > Only after a PR has been approved and merged to master should a binary be > uploaded anywhere. That's what I meant — but reusing buildbot for testing the PRs. > Our buildbot system was originally set up in 2011 by macOS

Re: CI system for PR builds

On 7 Apr 2018, at 07:47, Mojca Miklavec wrote: > No, because that would make the infrastructure that distributes binaries to > all our users susceptible to malicious PRs. How is reviewing a PR, then letting it build and, if it succeeds, uploading the binary, if not, reporting the results — diff

Re: CI system for PR builds

On 3 Apr 2018, at 18:04, Mojca Miklavec wrote: > Travis has lots of limitations, but it offers both (a) and (b) for free. Couldn't (b) be the current infrastructure? If I understood correctly previous posts, Travis builds PRs for 10.11-10.13, but then Buildbot builds the binaries that are being

Re: CI system for PR builds

On 3 Apr 2018, at 13:09, Rainer Müller wrote: > But what exactly do you think would be the benefit from such a complicated > setup (GitHub -> GitLab -> External Runner)? Testing? But hey, I only know MP's infrastructure from what I read in the list, TravisCI does wonders and everything's jolly

Re: CI system for PR builds

On 3 Apr 2018, at 02:20, Rainer Müller wrote: > Then please explain what this would offer us at all? I'll try. GitLab let's you have external runners (https://docs.gitlab.com/ee/ci/runners/README.html), while TravisCI offers a certain amount of pipeline minutes and only supports the currently s

Re: CI system for PR builds

On 2 Apr 2018, at 23:09, Clemens Lang wrote: > On Mon, Apr 02, 2018 at 08:43:52PM +0200, db wrote: >> GitLab 10.6 released with CI/CD for GitHub > Interesting, but I couldn't find any indication that this would support > builds on macOS. Do you have more info? I thin

Re: CI system for PR builds

On 2 Apr 2018, at 23:09, Clemens Lang wrote: > On Mon, Apr 02, 2018 at 08:43:52PM +0200, db wrote: >> GitLab 10.6 released with CI/CD for GitHub > Interesting, but I couldn't find any indication that this would support > builds on macOS. Do you have more info? Nope, bu

Re: CI system for PR builds

On 2 Apr 2018, at 22:53, Mojca Miklavec wrote: > I fail to find any info about available runners for hosted CI infrastructure. Is this what you're looking for? https://about.gitlab.com/features/github/ search for 'self-hosted'.

Re: CI system for PR builds

GitLab 10.6 released with CI/CD for GitHub https://about.gitlab.com/2018/03/22/gitlab-10-6-released/#open-source-projects

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

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 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 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 (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 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: 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 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 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 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: 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: 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: 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: 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: 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: 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: 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 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 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 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 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 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: 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 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: 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 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 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 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: 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: 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: 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: 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: 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: 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: 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: 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 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: 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: 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: 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: 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: 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: 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: 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?

reclaim and rleaves

Shouldn't reclaim use rleaves instead of unrequested? As of now I have to rerun reclaim in order to remove unnecessary ports.

Re: ansible replacement by py-ansible

On 15 Dec 2017, at 15:41, Andrew Fernandes wrote: > Not in the pypi dist! That's great. I guess, I'll have to make my own or look somewhere else.

Re: ansible replacement by py-ansible

On 15 Dec 2017, at 05:25, Andrew Fernandes wrote: > patched and committed in f5a44cbcb1 Weren't there also man pages?

Re: ansible replacement by py-ansible

On 14 Dec 2017, at 16:53, Joshua Root wrote: > It needs the attached change. Should I reopen #55229 and attach the diff?

ansible replacement by py-ansible

I tried upgrading ansible from 2.3.2.0.1_1 to 2.3.2.0.1_2 and it failed. The log showed a conflict with ansible (sic) so I cat'ed the portfile and noticed the ui_error in the pre-configure phase stating its replacement by py-ansible and some instructions. So I did install py-ansible and it faile

Re: Too many compilers needed for C++11

On 7 Dec 2017, at 14:51, Joshua Root wrote: > Looks correct to me; the system clang will be used for C++11 on 10.8 with > libc++ (assuming most recent possible Xcode). Ok. Out of curiosity, I tried on a 10.8-VM that's not set to build from source, with CLT, no Xcode — to install highlight and i

Re: Too many compilers needed for C++11

On 7 Dec 2017, at 07:29, Ryan Schmidt wrote: > They are, if you're running on an OS version where those dependencies are > added. Here's what I see: $ sw_vers ProductName:Mac OS X ProductVersion: 10.8.5 BuildVersion: 12F2560 $ port rdeps highlight The following ports are dependencies of h

Re: Too many compilers needed for C++11

On 7 Dec 2017, at 12:59, Mojca Miklavec wrote: > Nowadays many ports claim >Warning: All compilers are either blacklisted or unavailable; defaulting > to first fallback option > but do install nevertheless at the end. I would say that this is a bug in > either the portfiles or portgroups tha

Re: Too many compilers needed for C++11

On 6 Dec 2017, at 00:46, Ken Cunningham wrote: > clang/llvm 5.0 is the current cxx11 1.1 compiler, so that is what is being > called up. Shouldn't such portgroup dependencies be listed by `port rdeps`? I don't see it, for example, in highlight.

Re: base master and editing commands

On 4 Dec 2017, at 13:20, Rainer Müller wrote: > You are trying to build MacPorts against readline installed by MacPorts. Why can I build it against its own curl but not its own readline? Eventually, I temporarily deactivated readline and it built fine.

Re: base master and editing commands

On 4 Dec 2017, at 01:00, Joshua Root wrote: > So you want --enable-readline as well. I tried cleaning and rebuilding, and now I get the following error. readline.c:128:23: error: use of undeclared identifier 'username_completion_function'; did you mean 'rl_username_completion_function'?

Re: base master and editing commands

On 4 Dec 2017, at 01:00, Joshua Root wrote: > So you want --enable-readline as well. I just tried it and some of the commands still don't work: ^A, ^E, arrows — ^U, ^W work though.

Re: base master and editing commands

On 4 Dec 2017, at 01:00, Joshua Root wrote: > So you want --enable-readline as well. Thanks. In the guide 2.2.2. doesn't use this option, 2.2.3. does.

Re: base master and editing commands

On 4 Dec 2017, at 00:37, Joshua Root wrote: > Looks like you have a build without readline support? Hmm…, I just cloned base master and built it. Only option I added is --with-curlprefix=/opt/local to the configure phase.

base master and editing commands

Basic editing commands don't work in shell mode. macports-base $ port MacPorts 2.4.99 Entering shell mode... ("help" for help, "quit" to quit) [Code/macports-base] > syncc^H^H^A^E^K Fortunately ^U works. I haven't found an issue in the tracker.

Re: Force build on wrong builder

On 12 Oct 2017, at 22:23, Joshua Root wrote: > All old port versions are uninstalled after each build, so the deps will > never be outdated during a build. Also a build would have been triggered in > response to any earlier commit that updated one of the deps. Let's say, port A depends recursiv

Re: Force build on wrong builder

On 12 Oct 2017, at 16:13, Ryan Schmidt wrote: > On Oct 12, 2017, at 09:11, db wrote: >> >> Does a commit to a dependency trigger a rebuild of its rdependents? > Unfortunately no. We've been discussing that on the -infra list but I don't > think we found a solutio

Re: Force build on wrong builder

On 12 Oct 2017, at 14:37, Ryan Schmidt wrote: > The High Sierra builder has been busy building ports as commits come in. It > builds and deploys binaries not only for the port being modified, but also > for all of its dependencies recursively. Does a commit to a dependency trigger a rebuild of

Re: State of the GnuPG ports

On 10 Oct 2017, at 07:18, Leonardo Brondani Schenkel wrote: > On 2017-10-10 03:10, Helmut K. C. Tessarek wrote: >> On 2017-10-09 08:11, Rainer Müller wrote: >>> gnupg -> 2.2 >>> gnupg-devel -> 2.3 >>> gnupg1 -> 1.4 >> +1 > +1 +1

Re: Releasing 2.4.2

On 6 Oct 2017, at 18:54, Ryan Schmidt wrote: > Thanks, that was exactly the fix I was just going to suggest. I'll deploy > that, then 2.4.2 should be available within the hour. Sorry to hijack the thread. I just installed 2.4.2 from source and realised that rleaves didn't make it to it yet. Any

Re: virtual machine for 10.5 intel ?

On 3 Oct 2017, at 05:01, Ken Cunningham wrote: > if anyone would care to enlighten me on the best approach to making a VM for > 10.5 intel, I would appreciate it. This is the only system I have that I > can’t presently see a way to virtualize. At that time I wanted to do the same and found this

Re: Restoring from Time Machine backup relocates home directories

On 17 Sep 2017, at 00:15, Ryan Schmidt wrote: > File ownership can be preserved on disk images, but that ownership is > preserved by uid and gid, not by user name and group name. I suspected this but didn't know how it actually works on OS X. >> MP could also checked if the UIDs/GIDs are alread

Re: Restoring from Time Machine backup relocates home directories

On 16 Sep 2017, at 16:03, Rainer Müller wrote: > As you just run it on your system, you know how long that will take. > Clearly not an option to do this before/after every install/uninstall. Only those that create users. > And what would you gain from that? A free uid. They are not a scarce > re

Re: Restoring from Time Machine backup relocates home directories

On 15 Sep 2017, at 23:47, Ryan Schmidt wrote: > MacPorts and ports can add users, but MacPorts doesn't remove them. I'm not > sure how we could change that. Suppose you install a port that has a user > that needs to own some data, such as postresql96-server. You then uninstall > the port, which

Re: Restoring from Time Machine backup relocates home directories

On 15 Sep 2017, at 18:06, Ryan Schmidt wrote: > Not always, because many ports use local variables when setting the home > directory, so you then have to find the place in the Portfile where that > local variable is set. And also, many ports split the add_users invocation > over multiple lines,

Re: Restoring from Time Machine backup relocates home directories

On 15 Sep 2017, at 04:32, Ryan Schmidt wrote: > I recently reinstalled macOS and, during the setup process, restored from a > Time Machine backup. One would think that after restoration, the machine > would be in a state sufficiently similar to the one it was in at backup time, > but for our pu

Re: Switching cxx_stdlib for C++11 on legacy macOS

On 4 Sep 2017, at 20:16, Ken Cunningham wrote: > switch to libc++: > Benefits: > 1. most builds are identical to 10.9+, most portfiles need no changes. > Drawbacks: > 1. needs changes in macports infrastructure to support new buildbots and > pre-built binaries > 2. poorly-written software or Port

Re: Switching cxx_stdlib for C++11 on legacy macOS

On 3 Sep 2017, at 13:47, Rainer Müller wrote: > The other option to switch would be to just change the default of > cxx_stdlib with the next 2.x release, wipe all existing binary packages > and ask all existing users on legacy systems to uninstall, then > reinstall all their ports. Less work for d

Re: Why does macports require a migration across major version bumps?

On 30 Aug 2017, at 20:29, Clemens Lang wrote: > Use 'sudo port -f selfupdate' instead, which should also recompile your > version of MacPorts. > In theory, reinstalling MacPorts and using 'sudo port -t upgrade > outdated' after an OS update should thus have the same effect as the > migration inst

Re: get user's home

On 8 Aug 2017, at 02:12, Ryan Schmidt wrote: > path:-style dependencies are used when more than one port could satisfy the > dependency, in this case the development and stable versions of > bash-completion. Thanks, that cleared it up. Re ipfs, I left the startup item for the user to install

  1   2   >