<html><head></head><body><div></div><div>
<title></title>
<div dir="auto"><font face="Helvetica">Just as suggestion, there's a package manager named
Spack that is quite similar to Macports (and Brew) that is made for
HPC deployment on clusters, but I'm also using it for installing
software on Linux in my $HOME when I don't have admin rights. It
works already for Mac and it basically has all the pieces needed
for replicating Macports functionalities...
</font><div dir="auto"><font face="Helvetica"><br></font></div>
<div dir="auto"><font face="Helvetica">I'm not a great fan or replicating work so if
you're really thinking about rewriting the base in Python looking at Spack could be a great way. </font></div><div dir="auto"><font face="Helvetica">Spack at the moment does even “more” than Macports because it’s meant to install different toolchains baselines one next to each other (e.g. GCC 8 + MPICH + FFTW next to Intel Compiled stuff), but with configuration tweaks and Spack Views you can probably replicate Macports functionalities. I already contributed few packages and the class-based package system is really easy to tackle for writing new packages. Moreover the tool is backed by LLNL Computation Department. </font></div><div dir="auto"><font face="Helvetica"><br></font></div><div dir="auto"><font face="Helvetica">Just my two cents to a suggestion, it would be great to have the base written in Python … TCL is really obscure to me :)</font></div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Sat, 12 Jan 2019, 20:26 Mojca Miklavec
<<a href="mailto:mojca@macports.org">mojca@macports.org</a>
wrote:<br></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
Here's the summary of today's meeting.<br>
<br>
=== Next online meeting<br>
<br>
Scheduled two weeks from now (January 26th), with the stress on
GSOC.<br>
We'll adjust the timing based on requests to join from USA or<br>
Australia, please raise your hands if you want to join.<br>
<br>
=== MacPorts Meeting 2019<br>
<br>
We shortlisted some dates (Saturday - Wednesday):<br>
- 6.-10. April<br>
- 11.-15. May<br>
- 8.-12. June<br>
Aljaž is suggesting June to hopefully get nicer weather,
potentially<br>
the ability to go swimming etc.<br>
<br>
The idea is to organize the meeting in Trieste, Aljaž will try to
find<br>
a suitable place to stay. If you would like to join, please cast
the<br>
vote for your favourite date. If none of those dates suit you and
you<br>
would like to join, please let us know.<br>
<br>
=== Google Summer of Code<br>
<br>
* We are looking for volunteers to mentor the students.<br>
* We would probably not participate with more than one or two<br>
projects, but we will only apply if we get sufficient interest
from<br>
potential mentors (ideally those who know the base).<br>
* Me and Umesh could guide a student working on buildbot or
webapp,<br>
but that's not sufficient on itself to apply.<br>
* Jackson would require hardware to be able to help more :)<br>
* We need to attach "sample tasks" to all the ideas that we
are<br>
suggesting to students (for screening the students for their
fitness<br>
to work in GSOC).<br>
<br>
=== Software Freedom Conservancy<br>
<br>
We discussed joining SFC. I sent an email to the PortMgr, but
that<br>
list is slightly quiet :).<br>
We will repeat the initiative on this mailing list. It could be
nice<br>
to try if we could get some co-funding for the meeting.<br>
<br>
=== Travis<br>
<br>
* Zero recently made quite some improvements to our bot &
Travis<br>
infrastructure. Thank you very much!<br>
* Private repositories for binary packages are now
used.<br>
* Packages are always built from source.<br>
* Obsolete packages are no longer scheduled for build, just
to fail anyway.<br>
* Some improvement in the bot.<br>
* He is looking for some further suggestions that could improve our
experience.<br>
* (My not-too-serious suggestion was to ping participants
after two<br>
weeks of no activity, to simplify Perry's life :)<br>
* Zero was thinking of starting to work on a script that
could<br>
automatically update port version based on livecheck results
and<br>
automatically create a pull request. This would be a very
welcome<br>
addition.<br>
* My question was whether we could also automate
revbumping<br>
dependent ports, but this is slightly more challenging.<br>
* Zero is looking into the other tickets (four tickets are
currently<br>
open) and into automating releases. He asked if someone
(Clemens?)<br>
could create an account on Bintray, but he'll send the details
over<br>
the mailing list.<br>
* Zero asked if it was possible NOT to result in an error in
"port<br>
test" when a port doesn't have any tests defined. At the moment
he<br>
cannot enable running tests on Travis since that would almost
always<br>
result in a failure when the port didn't implement that
functionality,<br>
even if there was sufficient time left to run the tests.<br>
* Rainer promised to create ticket for base to support "port
bintest"<br>
which could test something like "binaryname --version" or do
some<br>
other simple test to check whether a port is working after it's
being<br>
installed. This could also be a potential GSOC task, even though
too<br>
small all by itself.<br>
<br>
=== MacPorts base<br>
<br>
(Looking for volunteers to rewrite the base to python to gain
more<br>
contributors :) :) :)<br>
Jackson will start drafting some introduction to programming
MacPorts base.<br>
<br>
=== Participants (in order of appearance)<br>
<br>
* umeshksingla (Umesh)<br>
* mojca (Mojca)<br>
* g5pw (Aljaž)<br>
* l2dy (Zero)<br>
* raimue (Rainer)<br>
* ijackson (Jackson)<br>
<br>
Thanks to everyone for participation, even if the schedule was a
bit<br>
messy today, sorry for the confusion :)<br>
<br>
Mojca<br>
<br>
<br>
On Sat, 12 Jan 2019 at 12:01, Mojca Miklavec <<a href="mailto:mojca@macports.org" rel="noreferrer">mojca@macports.org</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> I think I first messed up the addition and subtraction in time
zones<br>
> (last time it was apparently at 13:00 UTC), and then with
sending out<br>
> the email yesterday under the wrong address. I wanted to ask
if there<br>
> were any participants from the far east or west who wanted
to<br>
> participate, in that case we could shift the hour, but since
we only<br>
> had people from UTC+1 and UTC+5.5 who raised their hands,
we'll stick<br>
> with 15:00 UTC for now.<br>
><br>
> This is the calendar:<br>
><br>
> <a href="https://calendar.google.com/calendar/embed?src=9unkhredr302jroorlhusav0ko%40group.calendar.google.com&mode=AGENDA" rel="noreferrer noreferrer">https://calendar.google.com/calendar/embed?src=9unkhredr302jroorlhusav0ko%40group.calendar.google.com&mode=AGENDA</a><br>
><br>
> And this is for hangouts (last time we had a much shorter
link, I'm<br>
> unable to come up with that shorter one this time, but if
anyone knows<br>
> how, feel free to post something better):<br>
><br>
> <a href="https://calendar.google.com/event?action=TEMPLATE&tmeid=N2ZxcWFsbnFmcmtvcmxpYWVrMGxoc2s4MGQgOXVua2hyZWRyMzAyanJvb3JsaHVzYXYwa29AZw&tmsrc=9unkhredr302jroorlhusav0ko%40group.calendar.google.com" rel="noreferrer noreferrer">https://calendar.google.com/event?action=TEMPLATE&tmeid=N2ZxcWFsbnFmcmtvcmxpYWVrMGxoc2s4MGQgOXVua2hyZWRyMzAyanJvb3JsaHVzYXYwa29AZw&tmsrc=9unkhredr302jroorlhusav0ko%40group.calendar.google.com</a><br>
><br>
> Meeting notes will be collected here:<br>
> <a href="https://trac.macports.org/wiki/Meetings/2019-01-12" rel="noreferrer noreferrer">https://trac.macports.org/wiki/Meetings/2019-01-12</a><br>
><br>
> Topics:<br>
> - Google Summer of Code 18 & 19<br>
> - MacPorts Meeting in 2019<br>
> - Software Freedom Conservancy<br>
> - Review open pull requests and roadmap for base<br>
> - ... any other topics open for proposal?<br>
><br>
> Looking forward to see you soon,<br>
> Mojca<br></blockquote>
</div>
</div></body></html>