On 2018-03-11 23:54, Enrico Maria Crisostomo wrote:
>> However, when we are going to add more templates, lots of options will
>> be repeated in each of them. If we are later going to change any of
>> these, we have to do this in all templates. I am not sure how much of a
>> problem that will be.
>>
> On 12 Mar 2018, at 08:28, Ryan Schmidt wrote:
>
>
> On Mar 9, 2018, at 13:22, Enrico Maria Crisostomo wrote:
>
>> I pushed to GitHub a skeleton of the idea:
>>
>> https://github.com/emcrisostomo/macports-utils
>>
>> I've moved what I'm using to a new script to see what the end result lo
On Mar 9, 2018, at 13:22, Enrico Maria Crisostomo wrote:
> I pushed to GitHub a skeleton of the idea:
>
>https://github.com/emcrisostomo/macports-utils
>
> I've moved what I'm using to a new script to see what the end result looked
> like. If you want to try it, just grab the release tarba
> On 11 Mar 2018, at 16:40, Rainer Müller wrote:
>
> On 2018-03-09 20:22, Enrico Maria Crisostomo wrote:
>> I pushed to GitHub a skeleton of the idea:
>>
>>https://github.com/emcrisostomo/macports-utils
>>
>> I've moved what I'm using to a new script to see what the end result looked
>> l
On 2018-03-09 20:22, Enrico Maria Crisostomo wrote:
> I pushed to GitHub a skeleton of the idea:
>
> https://github.com/emcrisostomo/macports-utils
>
> I've moved what I'm using to a new script to see what the end result looked
> like. If you want to try it, just grab the release tarball her
Ken,
I pushed to GitHub a skeleton of the idea:
https://github.com/emcrisostomo/macports-utils
I've moved what I'm using to a new script to see what the end result looked
like. If you want to try it, just grab the release tarball here (if you don't
have the Autotools installed):
./con
Thanks Ryan for the explanation.
> On 7 Mar 2018, at 19:51, Ryan Schmidt wrote:
>
>
> On Mar 7, 2018, at 07:32, Rainer Müller wrote:
>
>> On 2018-03-07 11:32, Enrico Maria Crisostomo wrote:
>>> This is a little bit offtopic IMHO, anyway: I found surprising too that
>>> the github portgroup was
On Mar 7, 2018, at 07:32, Rainer Müller wrote:
> On 2018-03-07 11:32, Enrico Maria Crisostomo wrote:
>> This is a little bit offtopic IMHO, anyway: I found surprising too that
>> the github portgroup was not documented, given the high percentage of
>> software that I build out of github repositor
On 2018-03-07 11:32, Enrico Maria Crisostomo wrote:
> This is a little bit offtopic IMHO, anyway: I found surprising too that
> the github portgroup was not documented, given the high percentage of
> software that I build out of github repositories, and that's why I
> recently contributed the docum
I play in a different playground and primarily use either master, dev or
develop branches as I run with latest codebase available. ffmpeg, imagemagick,
opencv, clang6, openblas, etc. These get a lot of PRs everyday.
Having to update the Portfiles manually with latest hash and date/version is
This is a little bit offtopic IMHO, anyway: I found surprising too that the
github portgroup was not documented, given the high percentage of software that
I build out of github repositories, and that's why I recently contributed the
documentation of the github portgroup:
https://github.com/mac
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. When you're in it's difficu
Hi Ken,
I think it's a great idea. I'm maintaining a lot of software both on my
personal machines and at work using MacPorts and I've setup some local Makefile
targets to do some of this work. Perhaps I could contribute some work on this
area, but first I'd like to know what is it that we'd lik
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
Rainer
On 2018-03-06, at 7:19 AM, Joshua Root wrote:
>
> There's a fairly basic tool called portfile-gen in contrib. Improvements
> are certainly welcome.
That is indeed a step towards what I was thinking of.
I'll look at this.
Ken
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
On 2018-03-06, at 7:22 AM, G Alexander wrote:
> I like the auto calculate hashes
>
> For grabbing something from url sounds like having a lot of switches,
>
> for archive type and depedencies
>
I was kinda hoping that the archive type might be figured out from the tail of
the URL. All the u
Hi,
On 6 March 2018 at 15:58, Ken Cunningham wrote:
> It would be nice to have a command like
>
> port create URL
>
> that would download the URL, calc the checksums for it, and build a basic
> Portfile for it.
>
> It could ask for a category to use for the Port.
>
> In a more advance version, it
I like the auto calculate hashes
For grabbing something from url sounds like having a lot of switches,
for archive type and depedencies
what if link is a redirect to cdn, or something like Dropbox or symbolic
> On Mar 6, 2018, at 06:58, Ken Cunningham
> wrote:
>
> Best,
On 2018-3-7 01:58 , Ken Cunningham wrote:
> It would be nice to have a command like
>
> port create URL
>
> that would download the URL, calc the checksums for it, and build a basic
> Portfile for it.
>
> It could ask for a category to use for the Port.
>
> In a more advance version, it could
Hi Ken - I think that's a great idea. In "GNU Radio" land, we have such a tool
for creating out-of-tree GR modules, called "gr_modtool"; it's great for
setting up the skeleton for such OOT GR scripts. The end-user still has to fill
in many "blanks", but this tool provides the starting point. I c
21 matches
Mail list logo