Hi!
> > > For the moment, I'd suggest to let the two additional RUN_DEPENDS=
> > > lines in the Makefile as proposed.
> >
> > Can you try with
> >
> > USE_TEX=latex dvipsk
> >
> > and without the two additional RUN_DEPENDS ?
>
> I can confirm that the dependencies are now fine with the
El día Sunday, October 12, 2014 a las 04:56:00PM +0200, Kurt Jaeger escribió:
> Hi!
>
> > For the moment, I'd suggest to let the two additional RUN_DEPENDS=
> > lines in the Makefile as proposed.
>
> Can you try with
>
> USE_TEX=latex dvipsk
>
> and without the two additional RUN_DEPEN
El día Sunday, October 12, 2014 a las 04:56:00PM +0200, Kurt Jaeger escribió:
> Hi!
>
> > For the moment, I'd suggest to let the two additional RUN_DEPENDS=
> > lines in the Makefile as proposed.
>
> Can you try with
>
> USE_TEX=latex dvipsk
>
> and without the two additional RUN_DEPEN
> # poudriere bulk -j freebsd-head -p ports-muttprint print/muttprint
> ...
> [00:06:37] >> Built ports: print/muttprint
> [freebsd-head-ports-muttprint] [2014-10-12_15h40m55s] [committing:] Queued: 1
> Built: 1 Failed: 0 Skipped: 0 Ignored: 0 Tobuild: 0 Time: 0
El día Sunday, October 12, 2014 a las 04:56:00PM +0200, Kurt Jaeger escribió:
> Hi!
>
> > For the moment, I'd suggest to let the two additional RUN_DEPENDS=
> > lines in the Makefile as proposed.
>
> Can you try with
>
> USE_TEX=latex dvipsk
>
> and without the two additional RUN_DEPEN
Hi!
> For the moment, I'd suggest to let the two additional RUN_DEPENDS=
> lines in the Makefile as proposed.
Can you try with
USE_TEX=latex dvipsk
and without the two additional RUN_DEPENDS ?
Or did I miss that you already tried that ?
--
p...@opsec.eu+49 171 3101372
has more info about USE_TEX, so please check that file for your
> experiments.
Hi,
I did today:
I checked out a 2nd fresh ports tree with:
# poudriere ports -c -p ports-muttprint -m svn+http -B head
# cd /usr/local/poudriere/ports/ports-muttprint/
# svn info
...
Last Changed Rev: 370680
Last
ay, I see with SVN certain changes in ports/Mk/bsd.tex.mk touching our
issue. I will setup a new tree for poudriere and compile only
print/muttprint in it. Stay tuned :-)
Thanks for your time
matthias
--
Matthias Apitz | /"\ ASCII Ribbon Campaign:
E-mail: g...@unixare
Hi!
> > How do you invoke muttprint and what does it call and what does it do
> > in the end ? Does it really generate a .ps to send to the printer ?
>
> Hi,
>
> I'm using muttprint to print mail from the MUA mutt; the mail is piped
> into the configured print cmd:
[...]
Thanks, this helps.
>
El día Saturday, October 11, 2014 a las 06:28:57PM +0200, Kurt Jaeger escribió:
> Hi!
>
> > > mat@ mailed that
> > >
> > > USE_TEX=latex dvipsk
> > >
> > > should be used instead of the two additional run_deps.
> >
> > A side note:
> >
> > bapt switched from 'latex' to texlive:
> [...]
>
> >
On Sat, Oct 11, 2014 at 6:42 PM, Kurt Jaeger wrote:
> Hi!
>
>> Not sure what you are talking about, but USE_TEX=texlive doesn't exit.
>
> I think Matthias refers to this:
>
> https://lists.freebsd.org/pipermail/svn-ports-all/2014-April/054544.html
>
> where
>
> USE_TEX=texlive
>
> was committed.
Hi!
> Not sure what you are talking about, but USE_TEX=texlive doesn't exit.
I think Matthias refers to this:
https://lists.freebsd.org/pipermail/svn-ports-all/2014-April/054544.html
where
USE_TEX=texlive
was committed. I'm by no means an expert in the TeX ports universe,
so any hint is appr
ive in poudriere does not pull it in.
> Can you provide a build log to show this ?
Hi,
Not sure what you are talking about, but USE_TEX=texlive doesn't exit.
Cheers,
Antoine
>
>> I brought
>> this question up in freebsd-pkg@ but did not got any comments on this.
>>
&g
s.
>
> I can revoke the change in my VM / poudriere and send in a complete log
> of the compilation of print/muttprint if someone is willing to dig into.
Yes, please.
> For the moment, I have not found any other solution as the two
> additional lines.
Well, if it solves your p
s on this.
I can revoke the change in my VM / poudriere and send in a complete log
of the compilation of print/muttprint if someone is willing to dig into.
For the moment, I have not found any other solution as the two
additional lines.
Thx
matthias
--
Matthias Apitz
Hi!
> > I need print/muttprint to print my mails.
> > Should I file a PR with the patch or could someone commit it?
>
> A PR is always preferred for the audit trail. I committed it, with
> the change of maintainer mentioned below.
mat@ mailed that
USE_TEX=latex dvipsk
s
Hi!
> I need print/muttprint to print my mails. I'm using 11-CURRENT, ports
> from SVN and poudriere to build them. The Makefile of the port does not
> pull in enough latex infrastructure, a patch is below. With this it
> works fine.
>
> Should I file a PR with the patch
Hello,
I need print/muttprint to print my mails. I'm using 11-CURRENT, ports
from SVN and poudriere to build them. The Makefile of the port does not
pull in enough latex infrastructure, a patch is below. With this it
works fine.
Should I file a PR with the patch or could someone commit it
Hello,
This is on head with poudriere: I compiled and installed print/muttprint
but it does not work because it needs latex :-(
Thanks
matthias
--
Matthias Apitz | /"\ ASCII Ribbon Campaign:
E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail
WWW:
=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes.
Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/muttprint-0.72d_3.log :
building muttprint-0.72d_3 in directory /var/tinderbox/7-STABLE-FTP
maintained by: [EMAIL PROTECTED]
building for: 7.0-STABLE amd64
port directory: /usr/ports/print/muttprint
Make
20 matches
Mail list logo