Re: snapd

2016-06-17 Thread Sterling Smith
As long as we are on the topic of other package managers, about a year ago I switched to conda (http://conda.pydata.org/docs/intro.html) on linux for managing python and underlying c/fortran dependencies. I wondered if any MacPorts developers had pursued conda on Mac with any success. There is

Re: snapd

2016-06-17 Thread Mojca Miklavec
On 17 June 2016 at 18:32, Ryan Schmidt wrote: > > On Jun 17, 2016, at 11:24 AM, Alexey Kuznetsov wrote: > >> Universal “snap” packages launch on multiple Linux distros >> >> https://insights.ubuntu.com/2016/06/14/universal-snap-packages-launch-on-multiple-linux-distros/ >> >> Even OpenWRT on the li

Re: snapd

2016-06-17 Thread Brandon Allbery
On Sat, Jun 18, 2016 at 12:35 AM, Alexey Kuznetsov < kuznetsov.ale...@gmail.com> wrote: > I read emerying carefully. Very informative. But you missing a point. I'm > not talking why it is not possible. Do you think all Linux distoros more > compatible between each other than Mac with three build >

Re: snapd

2016-06-17 Thread Alexey Kuznetsov
On Sat, Jun 18, 2016 at 4:36 AM, Ryan Schmidt wrote: > Fink was written in 2000 shortly after the release of Mac OS X Public > Beta. MacPorts was started in 2002. Why didn't its creators instead > contribute to Fink? I don't know; I wasn't part of the project back then. A > note on the Fink web s

Re: [149404] trunk/dports/devel/zmq/Portfile

2016-06-17 Thread Ryan Schmidt
> On Jun 17, 2016, at 3:49 PM, strom...@macports.org wrote: > > Revision > 149404 > Author > strom...@macports.org > Date > 2016-06-17 13:49:27 -0700 (Fri, 17 Jun 2016) > Log Message > > zmq: update to version 4.1.5 > Modified Paths > > • trunk/dports/devel/zmq/Portfile > homepage

Re: snapd

2016-06-17 Thread Ryan Schmidt
On Jun 17, 2016, at 12:34 PM, Alexey Kuznetsov wrote: > > On Fri, Jun 17, 2016 at 8:26 PM, Ryan Schmidt wrote: >> Again: why? What problem are you trying to solve? > > I think snapd is a good point to try to start to be together. May be because > no one tried three separate build system exists

Re: PortGroup python 1.0 guidance

2016-06-17 Thread Sterling Smith
Ed, Could it make sense to divide up the project into a python part, and a non-python part as two ports? Just a thought. -Sterling On Jun 17, 2016, at 12:44PM, Edward Maros wrote: > I am working on a project that provides an interfaces to several > scripting languages. One of these is Python

PortGroup python 1.0 guidance

2016-06-17 Thread Edward Maros
I am working on a project that provides an interfaces to several scripting languages. One of these is Python. I have been working on using PortGroup python 1.0 to provide all the correct values for the python variant requested. The most notable is python.pkgd. The unfortunate side effect of using

Re: snapd

2016-06-17 Thread Brandon Allbery
On Fri, Jun 17, 2016 at 1:34 PM, Alexey Kuznetsov < kuznetsov.ale...@gmail.com> wrote: > I think snapd is a good point to try to start to be together. May be > because no one tried three separate build system exists on Mac. Why waste > people energy by supporting all of them instead of good collab

Re: snapd

2016-06-17 Thread Alexey Kuznetsov
On Fri, Jun 17, 2016 at 8:26 PM, Ryan Schmidt wrote: > Again: why? What problem are you trying to solve? I think snapd is a good point to try to start to be together. May be because no one tried three separate build system exists on Mac. Why waste people energy by supporting all of them instead

Re: snapd

2016-06-17 Thread Ryan Schmidt
On Jun 17, 2016, at 11:58 AM, Alexey Kuznetsov wrote: > > On Fri, Jun 17, 2016 at 7:42 PM, Brandon Allbery wrote: > >> You're missing the point that those distributions are all based on Linux, >> and Portfiles exist because OS X is not Linux and many packages need to be >> beat over the head t

Re: snapd

2016-06-17 Thread Alexey Kuznetsov
On Fri, Jun 17, 2016 at 7:42 PM, Brandon Allbery wrote: > > You're missing the point that those distributions are all based on Linux, > and Portfiles exist because OS X is not Linux and many packages need to be > beat over the head to build in the first place. Package formats are not the > proble

Re: snapd

2016-06-17 Thread Brandon Allbery
On Fri, Jun 17, 2016 at 12:38 PM, Alexey Kuznetsov < kuznetsov.ale...@gmail.com> wrote: > I think this is step in the right direction make all packages support for > the same format. Having same portfile format (.yaml format) for all distros > is very nice. You're missing the point that those di

Re: snapd

2016-06-17 Thread Ryan Schmidt
On Jun 17, 2016, at 11:38 AM, Alexey Kuznetsov wrote: > On Fri, Jun 17, 2016 at 7:32 PM, Ryan Schmidt wrote: > >> On Jun 17, 2016, at 11:24 AM, Alexey Kuznetsov wrote: >> >> > Universal “snap” packages launch on multiple Linux distros >> > >> > https://insights.ubuntu.com/2016/06/14/universal-sn

Re: snapd

2016-06-17 Thread Alexey Kuznetsov
I think this is step in the right direction make all packages support for the same format. Having same portfile format (.yaml format) for all distros is very nice. http://snapcraft.io/create/ -- AK On Fri, Jun 17, 2016 at 7:32 PM, Ryan Schmidt wrote: > > On Jun 17, 2016, at 11:24 AM, Alexey Ku

Re: snapd

2016-06-17 Thread Ryan Schmidt
On Jun 17, 2016, at 11:24 AM, Alexey Kuznetsov wrote: > Universal “snap” packages launch on multiple Linux distros > > https://insights.ubuntu.com/2016/06/14/universal-snap-packages-launch-on-multiple-linux-distros/ > > Even OpenWRT on the list. Why not join? Do I understand correctly that you

snapd

2016-06-17 Thread Alexey Kuznetsov
Universal “snap” packages launch on multiple Linux distros https://insights.ubuntu.com/2016/06/14/universal-snap-packages-launch-on-multiple-linux-distros/ Even OpenWRT on the list. Why not join? -- AK ___ macports-dev mailing list macports-dev@lists.m