Re: dlopen() and (non-support in) MacPorts

On 2018-3-19 10:55 , Mojca Miklavec wrote: > Hi, > > I'm maintaining the dvisvgm port which links against libgs and works > with ghostscript as expected. > > But I also compile that binary as a standalone one, as part of TeX > Live (maybe MacTeX rings a bell, even though I'm not the one providing

dlopen() and (non-support in) MacPorts

Hi, I'm maintaining the dvisvgm port which links against libgs and works with ghostscript as expected. But I also compile that binary as a standalone one, as part of TeX Live (maybe MacTeX rings a bell, even though I'm not the one providing MacTeX itself). That binary uses dlopen() to find libgs

Re: understanding macports

On 2018-03-18 21:12, Abhishek Kashyap wrote: > No,I think it should be implemented in port.tcl(macports-base) under > function *procaction_selfupdate { action portlist opts }.* > See there line no. 2758. port/port.tcl is the port client that implements the command line interface. All features shou

Re: understanding macports

I also have to add file to macports-ports /news/ but how does it implemented. On 19 March 2018 at 01:42, Abhishek Kashyap wrote: > No,I think it should be implemented in port.tcl(macports-base) under > function *proc action_selfupdate { action portlis

Re: understanding macports

No,I think it should be implemented in port.tcl(macports-base) under function *proc action_selfupdate { action portlist opts }.* See there line no. 2758. On 19 March 2018 at 01:31, Mojca Miklavec wrote: > On 18 March 2018 at 06:49, Abhishek Kashyap wrote: > > hey > > i want to confirm that I hav

Handling trac tickets, and submissions in particular

Dear Perry, You are doing an amazing job at keeping the pull request number down to a negligible number compared to the number of submitted requests. Do you have any suggestion how to effectively tackle 409 trac tickets with port submissions? Click "Port submissions" on https://trac.macports

Re: understanding macports

On 18 March 2018 at 06:49, Abhishek Kashyap wrote: > hey > i want to confirm that I have to add news items to contents of port or > anywhere else. > Please specify explicitly where we have to add. I guess that the most sensible place would be to put the news under macports-ports/resources/news. T

Re: Gsoc

On 18 March 2018 at 07:17, Abhishek Kashyap wrote: > hi > i am working on Announcements distributed over the ports tree ¶ Great, this would be a nice-to-have feature. > This is template of newsitem to be added to port tree. > > If anyone wants changes please specify it and give feedback.This refe

Re: How to fetch and extract patches in archives?

What? Macports supports most archives zip, gz, bz2, etc extract the patches from the tarball add them to the Portname/Portfile/files/*. You should probably manually apply the patches first to see if it breaks the build or fixes the issue. I would not blindly apply any Linux patch. On Sun, Mar 18

Re: How to fetch and extract patches in archives?

On 2018-03-18 13:22, Zero King wrote: > On Sun, Mar 18, 2018 at 12:48:59PM +0100, Rainer Müller wrote: >> On 2018-03-18 12:28, Zero King wrote: >>> On Sun, Mar 18, 2018 at 09:57:58AM +0100, Mojca Miklavec wrote: On 18 March 2018 at 08:33, Zero King wrote: I would add the patches to distfi

Re: How to fetch and extract patches in archives?

On Sun, Mar 18, 2018 at 12:48:59PM +0100, Rainer Müller wrote: On 2018-03-18 12:28, Zero King wrote: On Sun, Mar 18, 2018 at 09:57:58AM +0100, Mojca Miklavec wrote: On 18 March 2018 at 08:33, Zero King wrote: I would add the patches to distfiles and include debian site in master_sites. You then

Re: How to fetch and extract patches in archives?

On 2018-03-18 12:28, Zero King wrote: > On Sun, Mar 18, 2018 at 09:57:58AM +0100, Mojca Miklavec wrote: >> On 18 March 2018 at 08:33, Zero King wrote: >> I would add the patches to distfiles and include debian site in >> master_sites. You then need to keep your fingers crossed that the main >> dist

Re: How to fetch and extract patches in archives?

On Sun, Mar 18, 2018 at 09:57:58AM +0100, Mojca Miklavec wrote: On 18 March 2018 at 08:33, Zero King wrote: Hi, Port w3m needs patches from Debian to fix security issues. Currently, the patches are added to the ports tree and takes ~800KiB. Since its size will grow, I'd prefer to fetch the patc

Re: Relax port lint rule for patchfile naming

While we're here: > >> How will you distinguish patchfiles from others > The lint check in question doesn't look at the contents of files/, it > looks at the patchfiles option. what e.g. OpenBSD does is it has a patches/ subdirectory in the port dir. Anything in there is a patch to be applied. N

Re: How to fetch and extract patches in archives?

On 18 March 2018 at 08:33, Zero King wrote: > Hi, > > Port w3m needs patches from Debian to fix security issues. Currently, > the patches are added to the ports tree and takes ~800KiB. Since its > size will grow, I'd prefer to fetch the patches from Debian archives > (e.g. w3m_0.5.3-36.debian.tar.x

How to fetch and extract patches in archives?

Hi, Port w3m needs patches from Debian to fix security issues. Currently, the patches are added to the ports tree and takes ~800KiB. Since its size will grow, I'd prefer to fetch the patches from Debian archives (e.g. w3m_0.5.3-36.debian.tar.xz). I tried to add the archive and ${workpath}/.../02