python port - use pypi or github

When writing a python port, what is best practice for one that's on both PyPI and GitHub, use pypi2port or portgroups github+python?

Re: python port - use pypi or github

On 10 Apr 2017, at 12:59, Clemens Lang wrote: > It's up to you, really. pypi2port might be easier, because it auto-generates > most > of the boilerplate and is better tested, since most python ports use PyPI. Ok, I just want to avoid having too much divergence between current

recursively copy docs

I want to recursively copy a port's documentation which has nested dirs. Is there any caveat for using exec cp -R ${worksrcpath}/sphinx-doc ${destroot}${docdir} instead of the more canonical form in the wiki? https://trac.macports.org/wiki/PortfileRecipes#doc

Re: recursively copy docs

On 29 Jul 2017, at 20:39, Ryan Schmidt wrote: > copy ${worksrcpath}/sphinx-doc ${destroot}${docdir} That macro works, but file copy errored each time I tried it before.

reinplace first occurrence

I checked portfile's man page and peaked at the source, but couldn't figure out yet, why these forms don't work. https://stackoverflow.com/a/11458836/2167331 In the meantime, I worked around it, but I'd still like to know how to do it.

Re: reinplace first occurrence

On 3 Aug 2017, at 18:46, Ryan Schmidt wrote: > You could run a two-command sed manually (with system, not reinplace). Or > maybe you can use awk, or an ed script. This works. Caveat emptor: || (empy RE) doesn't work and range seems to start on first line, not on its

Re: registry with multiple portfiles

On 13 Jul 2017, at 18:08, Joshua Root wrote: > Fixed in master: > I understand that there's no additional name field for subports in the registry and that they have the same hash. But

Re: registry with multiple portfiles

On 17 Jul 2017, at 10:38, Joshua Root wrote: > Don't delete anything from the database, its contents are correct (and have > been the whole time). You can delete the portfiles that are in a directory > named after a port (or version of a port) that is not installed. Those

Re: install doc with python group

On 11 Jul 2017, at 14:44, Joshua Root wrote: > Only the subports like py27-setuptools_hg and py35-setuptools_hg are supposed > to install any files. py-setuptools_hg is a stub port, and as such has no > distfiles and thus no extracted sources. I know why it fails. The stub

registry with multiple portfiles

Is it normal or expected to have multiple portfiles for the same port in the registry?

Re: registry with multiple portfiles

On 11 Jul 2017, at 16:16, Joshua Root wrote: > How do the files differ? Is one not referenced in the registry database? port cat shows the right file. I think I might explain this case — but not others. While writing the portfile for py-ipaddr in vim I saved it and stopped

Re: registry with multiple portfiles

On 11 Jul 2017, at 19:21, Joshua Root wrote: >> I think I might explain this case — but not others. While writing the >> portfile for py-ipaddr in vim I saved it and stopped the process, then >> installed/uninstalled the port and made some corrections in the portfile, >>

Re: registry with multiple portfiles

On 11 Jul 2017, at 18:40, db <iams...@gmail.com> wrote: > While writing the portfile for py-ipaddr in vim I saved it and stopped the > process, then installed/uninstalled the port and made some corrections in the > portfile, repeat. I tried this with another port while monitori

Re: tarball link when using python group

On 9 Jul 2017, at 23:29, Joshua Root wrote: > Solution 2: Use the github portgroup, which takes care of the idiosyncrasies > of fetching from github. It's fine to use at the same time as the python > portgroup, see e.g. py-alabaster. Thanks for the reference. I was missing

Re: registry with multiple portfiles

anually checked the reg db yet.

Re: [GSoC] migration

On 20 Jul 2017, at 06:04, Bradley Giesbrecht wrote: > Snapshot and restore should be able to be executed without migrate. I have a question and I haven't been following in detail this GSoC, so bear with me. Could snapshot and restore be used to rollback to a previous

Re: [GSoC] migration

On 22 Jul 2017, at 03:01, Umesh Singla wrote: > I don't know, in the above example, what do you mean when you say "..you > realize that from its deps..", like, realize how? I am just asking this if > there's some other way to get info on the latest modifications that

Re: [GSoC] migration

On 27 Jul 2017, at 21:21, Bradley Giesbrecht wrote: > Migration will uninstall all installed ports and then install all the ports > from the snapshot Yes, but I'm talking about using snapshot and restore at different times with ports being updated between them, likely

Re: [GSoC] migration

On 27 Jul 2017, at 00:35, Umesh Singla wrote: > Hi Josh >> We don't have version dependencies so no, this sort of check is not possible >> a priori. Breakage will be caught by rev-upgrade after the fact in many >> cases (and if it is set to rebuild automatically, it

Re: [GSoC] migration

On 21 Jul 2017, at 13:02, Umesh Singla wrote: > Unless we have a snapshot of the previous state, that is, before it got > hampered. > But then again, we reinstall all the ports presently. At this time, it could > be hard for me to detect what went wrong while sync or

env python - port select or reinplace

What should I use to reference the python binary, put notes to use port select or rewrite the interpreter directive?

Re: pypi2port and python supported versions

On 24 Apr 2017, at 19:10, Mojca Miklavec wrote: > In short: > - we probably need a bit more effort to bring all modules to 3.6 > - we probably need to review which entries may go from py-graveyard > and potentially change the others to default to 36 rather than 34

Re: get user's home

On 4 Aug 2017, at 22:58, Joshua Root wrote: > Suppose a port is built on the buildbot. The user is 'buildbot' and so the > value of $user_home will be something like '/Users/buildbot'. During testing I didn't thoroughly checked that env var there. I suppose, it could be

Re: get user's home

On 4 Aug 2017, at 16:05, Joshua Root wrote: > Should be in $user_home (if it could be determined, which is not guaranteed). > But why do you need it? The user installing the port is not necessarily the > one that will use it. That worked, thanks. I used it for an env var's

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

Re: get user's home

On 7 Aug 2017, at 20:03, Bradley Giesbrecht <pixi...@macports.org> wrote: >> On Aug 5, 2017, at 3:55 AM, db <iams...@gmail.com> wrote: >>> docker-machine's port, although I don't quite grasp what depends_run-append >>> exactly does there. > Depends_run-a

Re: get user's home

On 7 Aug 2017, at 23:03, Joshua Root wrote: > Dependency specifications are documented here: > I already read that too, but don't see why in case of docker-machine a path dependency

get user's home

How can I get the user's home, the flesh and blood bot's? set home$::env(HOME) righteously returns /opt/local/var/macports/home/

Re: Python 3.4

On 8 May 2017, at 18:36, m...@macports.org wrote: >> - Should we actively remove 34 subports? > When py35 and py36 have more sub-ports, then yes. I wonder how many of those are maintained, of these how many actually get updated and how many are non-maintained at all.

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

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

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

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

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

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

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: Force build on wrong builder

On 12 Oct 2017, at 16:13, Ryan Schmidt <ryandes...@macports.org> 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 > t

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

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

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 >

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

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?

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 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

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: 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 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. 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

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

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

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: 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: reclaim and rleaves

On 15 Dec 2017, at 15:51, db <iams...@gmail.com> 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 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

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

On 22 Feb 2018, at 11:32, Umesh Singla <umeshksin...@macports.org> wrote: > On Thu, Feb 22, 2018 at 12:26 AM, db <iams...@gmail.com> wrote: > On 21 Feb 2018, at 17:33, Mojca Miklavec <mo...@macports.org> wrote: > > - New website! > Homebrew/Linuxbrew's are go

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 :) :)

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

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

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: 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 <iams...@gmail.com> wrote: > On 2 Jan 2018, at 22:51, Ken Cunningham <ken.cunningham.web...@gmail.com> > wrote: >> Found a consistent trigger. >> If safari is _not_ running: >> "port gohome gtk3" -> brings up “A

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.

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

Re: Changing default cxx_stdlib to libc++

On 9 Mar 2018, at 15:21, Joshua Root <j...@macports.org> wrote: > On 2018-3-9 20:38 , db wrote: >> On 9 Mar 2018, at 01:27, Ryan Schmidt <ryandes...@macports.org> wrote: >>> When would we run this script to delete libstdc++ archives? Presumably, >>> a

Re: Changing default cxx_stdlib to libc++

On 11 Mar 2018, at 02:47, "Kenneth F. Cunningham" <ken.cunningham.web...@gmail.com> 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 defec

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

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

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

Re: Changing default cxx_stdlib to libc++

On 12 Mar 2018, at 21:35, Ryan Schmidt <ryandes...@macports.org> 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. > W

Re: Changing default cxx_stdlib to libc++

On 13 Mar 2018, at 15:22, Ryan Schmidt <ryandes...@macports.org> 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 updat

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 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

Re: Changing default cxx_stdlib to libc++

On 10 Mar 2018, at 00:09, Joshua Root <j...@macports.org> 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 >>

Re: Changing default cxx_stdlib to libc++

On 10 Mar 2018, at 18:06, "Kenneth F. Cunningham" <ken.cunningham.web...@gmail.com> 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

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

om our template for the next PR build. > 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 interpretati

Re: Changing default cxx_stdlib to libc++

On 15 Mar 2018, at 05:19, Ryan Schmidt <ryandes...@macports.org> 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

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 <rai...@macports.org> 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

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

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

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,

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

Re: CI system for PR builds

On 8 Apr 2018, at 13:18, Ryan Schmidt <ryandes...@macports.org> 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 >> qui

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

Re: CI system for PR builds

On 8 Apr 2018, at 13:50, Ryan Schmidt <ryandes...@macports.org> 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 automat

Re: CI system for PR builds

On 8 Apr 2018, at 12:42, Zero King <l...@macports.org> 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 &g

Re: CI system for PR builds

On 10 Apr 2018, at 20:07, Mojca Miklavec <mo...@macports.org> 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

Re: CI system for PR builds

On 11 Apr 2018, at 15:44, Mojca Miklavec <mo...@macports.org> 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 >>>>

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

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

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

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

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

Re: CI system for PR builds

On 2 Apr 2018, at 23:09, Clemens Lang <c...@macports.org> 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 mo

Re: CI system for PR builds

On 2 Apr 2018, at 23:09, Clemens Lang <c...@macports.org> 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 mo

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

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

  1   2   >