Re: Port submission for aidadoc

Mojca, thank you very much for reviewing this port. The other two checksums (if needed) are md528acc622599ae70bd9027fd80cf9f9b8 sha1aece1dbfdc342c63995a1bf7d7de525067038748 I don’t know why the download fails. Indeed I already have a dist file locally in

Re: Port submission for aidadoc

On 2018-3-7 06:52 , Bernard Desgraupes wrote: > I don’t really understand how the master-sites command works when it says > master_sitessourceforge:projects/aidadoc/files/${version}/ > > The « real » download URL is >

Re: request for port create command, to build a portfile from a URL

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

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

Buildbot idea(s) for GSOC

Dear Umesh, In case we would get any good students in that area, I would be grateful if someone would work on improving buildbot core & front-end in close collaboration with mentors directly from buildbot. I added this one idea on the list, but it needs some polishing:

Re: request for port create command, to build a portfile from a URL

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

Re: Port submission for aidadoc

I'd set a no cache flag so you don't get lots of cookie and cache garbage > On Mar 6, 2018, at 22:15, Bernard Desgraupes wrote: > > Dear Joshua, > > thank you for the insight. Everything is clear now and I discover the -I and > -L options of curl by the way, very handy

Re: [macports-ports] branch master updated: irssi: perl5.26 revbump

On Tue, Mar 06, 2018 at 04:08:04AM -0600, Ryan Schmidt wrote: On Mar 3, 2018, at 20:59, Zero King wrote: Zero King (l2dy) pushed a commit to branch master in repository macports-ports. https://github.com/macports/macports-ports/commit/9f045bef9d96ad58591bcb71dbf2fc3a67303f82 The following

Re: [macports-ports] branch master updated: irssi: perl5.26 revbump

On Mar 6, 2018, at 04:18, Zero Kingwrote: > On Tue, Mar 06, 2018 at 04:08:04AM -0600, Ryan Schmidt wrote: >> >> On Mar 3, 2018, at 20:59, Zero King wrote: >> >>> Zero King (l2dy) pushed a commit to branch master >>> in repository macports-ports. >>> >>> >>>

Re: Port submission for aidadoc

On 2018-3-6 19:27 , Mojca Miklavec wrote: > I have a question for others: what's the "correct" way to run > autoheader > autoconf > before configure? We do have autoconf.cmd for example, but I'm not > sure about the best way to run more than one commands (unless I misuse > automake.cmd :)

Re: Port submission for aidadoc

So, if I understand correctly, writing: use_autoreconfyes would enough to replace the following: pre-configure { system -W ${build.dir} autoheader } use_autoconfyes Am I right ? Thanks, Bernard Le 6 mars 2018 à 10:17, Joshua Root a écrit : > On

Re: request for port create command, to build a portfile from a URL

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

Re: request for port create command, to build a portfile from a URL

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

Re: request for port peg command, to lock down a port at the currently installed version

I've seen this in other managers as "pin". Anyway, this gets tricky with managing dependencies. As you say, this would probably need to copy the current portfile, but it would also need to pin and copy anything that depends or is dependent on this port. And that's going to extend recursively out

Re: request for port create command, to build a portfile from a URL

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 >

Re: request for port create command, to build a portfile from a URL

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,

request for port create command, to build a portfile from a URL

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 extract the URL and do some quick analysis on it. if

Re: Port submission for aidadoc

On 6 March 2018 at 10:47, Joshua Root wrote: > On 2018-3-6 20:23 , Bernard Desgraupes wrote: >> So, if I understand correctly, writing: >> use_autoreconfyes >> >> would enough to replace the following: >> pre-configure { >> system -W ${build.dir} autoheader >> } >> use_autoconf

request for port peg command, to lock down a port at the currently installed version

It is fairly common for users to find an update to a port that won't build on their system for some reason. It would be nice to have a simple command, like port peg PORTNAME that stops the port from attempting to update until the peg is released. Such a command does exist in other package

Re: request for port create command, to build a portfile from a URL

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

Re: Port submission for aidadoc

On 6 March 2018 at 09:10, Bernard Desgraupes wrote: > Dear Mojca, > > I have made the recommended fixes and have just been attaching the modified > Portfile (added as Portfile.2). > This is Ticket #55808: https://trac.macports.org/ticket/55808 Thanks, but for some reason I'm unable to download

Re: Port submission for aidadoc

Dear Mojca, I have made the recommended fixes and have just been attaching the modified Portfile (added as Portfile.2). This is Ticket #55808: https://trac.macports.org/ticket/55808 cheers, Bernard Le 5 mars 2018 à 12:22, Mojca Miklavec a écrit : > Dear Bernard, > > On

Re: Port submission for aidadoc

On 2018-3-6 20:23 , Bernard Desgraupes wrote: > So, if I understand correctly, writing: > use_autoreconfyes > > would enough to replace the following: > pre-configure { > system -W ${build.dir} autoheader > } > use_autoconfyes > > Am I right ? In most cases yes. - Josh

Re: [macports-ports] branch master updated: irssi: perl5.26 revbump

On Mar 3, 2018, at 20:59, Zero King wrote: > Zero King (l2dy) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/9f045bef9d96ad58591bcb71dbf2fc3a67303f82 > > The following commit(s) were added to refs/heads/master by this