Alpine not displaying UTF-8

[Dave Horsfall]

I upgraded my Alpine to 2.21 (from 2.20) recently, now it is no longer 
displaying UTF-8 characters (yes, I have it set).  Anyone else noticed 
this?  I need to know whether it's a port bug or an upstream bug, so I 
know who to beat up.

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: synth: Error opening terminal: xterm

[Anton Shterenlikht]

> From: Baho Utot 
> Date: Wed, 12 Jul 2017 21:09:11 -0400
>
>
>
> On 7/12/2017 7:59 AM, Anton Shterenlikht wrote:
> > I'm starting using synth, never used it before.
> > I get this error:
> >
> > # synth build net/mpich
> > Error opening terminal: xterm.
> as a regular user open xterm
> then do the fololwing
> su -
> synth just-build /net/mpich
> or if you have doas and doas configured then
> doas synth just-build net/mpich

It turned out ncurses was the problem.
Switching ncurses off via "synth configure"
solved this problem.

I also tried one of my other boxes, and there
I don't get this problem. So it seems something
is indeed broken on this box, something to do
with ncurses...

Thanks

Anton

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: synth: Error opening terminal: xterm

[Baho Utot]

On 7/12/2017 7:59 AM, Anton Shterenlikht wrote:

I'm starting using synth, never used it before.
I get this error:

# synth build net/mpich
Error opening terminal: xterm.

as a regular user open xterm
then do the fololwing
su -
synth just-build /net/mpich
or if you have doas and doas configured then
doas synth just-build net/mpich



I'm supposed to run synth as root, right?
Is synth trying to open another xterm as root?

I've never allowed root access to a display:

# xterm
Warning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm: Xt error: Can't open display: %s
xterm: DISPLAY is not set

Am I wrong?



I run synth from a non-root account using sh and a script that uses doas

I am going to put all my scripts on github when I get the time.


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: make install for print/texinfo fails on -CURRENT

[Stefan Esser]

Am 12.07.17 um 18:11 schrieb David Naylor:
> On Tuesday, 11 July 2017 08:47:17 Bob Willcox wrote:
>> Hmm, I just tried running synth on my test system again (this is the system
>> that I successfully built and install texinfo on just a bit ago) and synth
>> still fails with the same build errors as before. I'm not all that familiar
>> with synth, but it appears that it may be working with some old stuff.
> 
> Hi
> 
> (Replying to a random email)
> 
> I've encountered the exact same issue while building the i386 packages for 
> wine.  Once I forced a rebuild of _all_ texinfo dependencies, installation 
> worked.  
> 
> I suspect an ABI change in -CURRENT that broke a dependency (sounds like perl 
> based on the thread).  

I had a problem with subversion after the upgrade to 1.9.6, and this
was due to an incompatibility with the apr library, which had not been
rebuilt for some time.

Seems that this is fall-out from the ino64 changes. Seems that while
symbol versioning allows old libraries to access struct stat as it was
before the change, this struct stat passed to a freshly built binary
(or library) by reference will cause obvious failures.


So, if you compile any port after the ino64 change, better make sure
that all referenced libraries (that operate on struct stat and might
pass such a struct to a fresh binary) have been rebuilt before.

As long as binary packages are built on a pre-ino64 machine, the
resulting packages ought to work on any -CURRENT system. But if you
build any port that references a library installed by such a package,
you risk mixing different versions of struct stat. This will continue
to be a problem as long as the -CURRENT package builders are pre-ino64.

If the package builders are upgraded to support ino64, all ports that
call stat() (or other functions with call signature affected by ino64)
should have PORTREVISION bumped, as should all ports depending on them.

Regards, STefan
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: make install for print/texinfo fails on -CURRENT

[David Naylor]

On Tuesday, 11 July 2017 08:47:17 Bob Willcox wrote:
> Hmm, I just tried running synth on my test system again (this is the system
> that I successfully built and install texinfo on just a bit ago) and synth
> still fails with the same build errors as before. I'm not all that familiar
> with synth, but it appears that it may be working with some old stuff.

Hi

(Replying to a random email)

I've encountered the exact same issue while building the i386 packages for 
wine.  Once I forced a rebuild of _all_ texinfo dependencies, installation 
worked.  

I suspect an ABI change in -CURRENT that broke a dependency (sounds like perl 
based on the thread).  

Regards

signature.asc
Description: This is a digitally signed message part.

strip: elf_strptr failed: Invalid argument

[Gergely Czuczy]

Hello,

I'm trying to build packages on an rpi3, on a freshly build image (with
crochet), and when it's trying to build pkg from ports, I'm getting the
following error message:

libtool: link: cc -D_BSD_SOURCE -I../libpkg -I../libpkg -I../compat
-I../external/libucl/klib -I../external/uthash -I../external/expat/lib
-DGITHASH=\"\" -O2 -pipe -Wno-error -fno-strict-aliasing -Wall
-Wno-unused-function -D_BSD_SOURCE -DINET6=1 -Wl,--enable-new-dtags -o
.libs/pkg pkg-add.o pkg-alias.o pkg-annotate.o pkg-audit.o
pkg-autoremove.o pkg-backup.o pkg-check.o pkg-clean.o pkg-config.o
pkg-convert.o pkg-create.o pkg-delete.o pkg-event.o pkg-fetch.o
pkg-globals.o pkg-info.o pkg-install.o pkg-lock.o pkg-main.o
pkg-plugins.o pkg-query.o pkg-register.o pkg-repo.o pkg-rquery.o
pkg-search.o pkg-set.o pkg-shell.o pkg-shlib.o pkg-ssh.o pkg-stats.o
pkg-update.o pkg-updating.o pkg-upgrade.o pkg-utils.o pkg-version.o
pkg-which.o  ../libpkg/.libs/libpkg.so ../compat/.libs/libbsd_compat.a
-lutil -lssl -lcrypto -lm -lelf -ljail -larchive -lz -lbz2 -llzma
-Wl,-rpath -Wl,/usr/local/lib
 /bin/mkdir -p '/usr/ports/ports-mgmt/pkg/work/stage/usr/local/etc'
 install  -m 0644 pkg.conf.sample
'/usr/ports/ports-mgmt/pkg/work/stage/usr/local/etc'
 /bin/mkdir -p '/usr/ports/ports-mgmt/pkg/work/stage/usr/local/sbin'
 STRIPPROG='strip' /bin/sh ../libtool   --mode=install /bin/sh
/usr/ports/ports-mgmt/pkg/work/pkg-1.10.1/install-sh -c -s pkg-static
pkg '/usr/ports/ports-mgmt/pkg/work/stage/usr/local/sbin'
libtool: install: /bin/sh
/usr/ports/ports-mgmt/pkg/work/pkg-1.10.1/install-sh -c -s pkg-static
/usr/ports/ports-mgmt/pkg/work/stage/usr/local/sbin/pkg-static
strip: elf_strptr failed: Invalid argument
*** Error code 1

Stop.
make[5]: stopped in /usr/ports/ports-mgmt/pkg/work/pkg-1.10.1/src
*** Error code 1

Strange part, it says it's stripped already:

root@build:/usr/ports/ports-mgmt/pkg # file -s
./work/pkg-1.10.1/src/pkg-static
./work/pkg-1.10.1/src/pkg-static: ELF 64-bit LSB executable, ARM
aarch64, version 1 (FreeBSD), statically linked, stripped

However, trying to strip(1) manually reproduces the error:

# strip ~/pkg-static.1
strip: elf_strptr failed: Invalid argument

ktrace didn't reveal anything about the failing elf_strptr(3) call.

The system is:

FreeBSD build.aegir 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r320657: Tue
Jul  4 22:28:33 CEST 2017
ae...@marvin.harmless.hu:/tank/rpi3/crochet/work/obj/arm64.aarch64/tank/rpi3/src/sys/AEGIR
arm64

Could someone please help me with this? I don't really know how to solve
this, or where to start looking. Usually building pkg works out of box.

Best regards,
Gergely




___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

CfT: glusterfs 3.11.1 port

[Craig Butler]

Hello Folks

I have been trying to update the glusterfs port to bring it up to the
latest version 3.11.1

I would appreciate if folks would build and install the port... test
and report back any issues.

The glusterfs client needs FreeBSD 11.1-RC2 or later (fuse fixed in
r320451)

Tarball or diff available at;
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220674

Thanks

Craig Butler
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Update failure E000022 after upgrade to subversion 1.9.6

[duglas]

Thank you all kindly for you input.

I'd not previously set any locale at all. Setting my locale in 
~/.login_conf as below enables me to run svn updates again.


me:\
:charset=UTF-8:\
:lang=en_AU.UTF-8:\
:setenv=LC_COLLATE=C:

I chose my lang by checking the output from,
locale -a | grep '\.UTF-8$'

Strangely the "svn status" command then seg faulted on me which it 
didn't previously. This seemed to begin after the 1.9.6 update and 
before (and after) setting my locale as above.


I then rebuilt devel/apr1 and devel/subversion as mentioned by Stefan.

Things seem healthier again with both "svn update" and "svn status".

However I now get the following when running "svn update /usr/ports"
svn: E175002: Unexpected HTTP status 400 'Bad Request' on '/ports/!svn/me'
Perhaps this is unrelated to the above issues I was experiencing.

I'd meant to respond sooner but my incompetence and unfamiliarity with 
the mailman system prevented me doing so promptly ;)


On 12/07/2017 9:12 PM, Stefan Esser wrote:

Am 12.07.17 um 07:42 schrieb Rainer Hurling:

Hi duglas@

I had the same problem. I completely solved it by rebuilding the
dependency chain of devel/subversion:

portmaster serf-1.3.9_1 expat-2.2.1 gettext-runtime-0.19.8.1_1
apr-1.5.2.1.5.4_2 sqlite3-3.19.3_1 subversion-1.9.6

Probably, only one of them is the culprit, but I haven't testet ;)

I have, and it appears to have been devel/apr1 ...

After rebuilding first apr and then subversion, the problem is resolved
on my system.

The cause seems to have been the ino64 change, which is visible from the
userland. Library versioning should take care of that, but that does not
work, if subversion wants the new version and apr needs the old one ...

Other ports could be affected as well, if they link against a library
that needs an old version of a C library function, while the binary was
built for the new call signature.

As long as ports are built with or without the ino64 change, they should
continue to work (and thus, -STABLE packages are not affected).

Regards, STefan



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

synth: Error opening terminal: xterm

[Anton Shterenlikht]

I'm starting using synth, never used it before.
I get this error:

# synth build net/mpich
Error opening terminal: xterm.

I'm supposed to run synth as root, right?
Is synth trying to open another xterm as root?

I've never allowed root access to a display:

# xterm 
Warning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm: Xt error: Can't open display: %s
xterm: DISPLAY is not set

Am I wrong?

Anton
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Update failure E000022 after upgrade to subversion 1.9.6

[Stefan Esser]

Am 12.07.17 um 07:42 schrieb Rainer Hurling:
> Hi duglas@
> 
> I had the same problem. I completely solved it by rebuilding the
> dependency chain of devel/subversion:
> 
> portmaster serf-1.3.9_1 expat-2.2.1 gettext-runtime-0.19.8.1_1
> apr-1.5.2.1.5.4_2 sqlite3-3.19.3_1 subversion-1.9.6
> 
> Probably, only one of them is the culprit, but I haven't testet ;)

I have, and it appears to have been devel/apr1 ...

After rebuilding first apr and then subversion, the problem is resolved
on my system.

The cause seems to have been the ino64 change, which is visible from the
userland. Library versioning should take care of that, but that does not
work, if subversion wants the new version and apr needs the old one ...

Other ports could be affected as well, if they link against a library
that needs an old version of a C library function, while the binary was
built for the new call signature.

As long as ports are built with or without the ino64 change, they should
continue to work (and thus, -STABLE packages are not affected).

Regards, STefan
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

PR looking for committer

[Nikolay Korotkiy]

Hi All,

Could someone committer please have a look at this?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214758.

-- 
Best regards,
Nikolay



signature.asc
Description: OpenPGP digital signature

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
devel/aunit | 2016| 2017
+-+
www/nginx   | 1.12.1  | 1.13.3
+-+
www/phpmustache | 2.11.1  | v2.12.0
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Making port check-plist errors

[Kurt Jaeger]

Hi!

> make makeplist
[...]

You have to redirect hat into the pkg-plist file, like this:

make makeplist > new-plist

Then edit to fix issues (there's always one to force
you to visually inspect the file 8-)

vi new-plist

and name the final file pkg-plist.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Look for a committer

[Jov]

Hi Hackers,

I made a new port named /deve/bear, which is a tool that generates a
compilation database for clang tooling. It is useful for
clang-tidy/clang-check with non-cmake project.

PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220475

WWW: https://github.com/rizsotto/Bear

QA:
portlint -AC
looks fine.
poudriere testport passed on 11.0R-amd64

Thanks versy much!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: RetroArch-1.3.6_7

[David Demelier]

I'll update it.

-- 
David Demelier

Le 11 juil. 2017 6:02 AM, "bluesky"  a écrit :

> Hello. The Retroarch port seems a bit out of date. Retroarch is on version
> 1.6.0 now.
>
> Thank you.
>
>
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Making port check-plist errors

[blubee blubeeme]

I did that.

The steps that I take are write the makefile with these contents:
NO_BUILD=   yes
NO_WRKSUBDIR=   yes
PLIST_SUB=   LINUXBASE=${LINUXBASE}
USES=   linux
USE_LINUX=   cups-libs jpeg

do-install:
# (cp -r ${WRKSRC}/opt/${PORTNAME} ${STAGEDIR}/${PORTNAME}}
(gunzip ${WRKSRC}/opt/${PORTNAME}/ppds/Epson/*)
(find ${WRKSRC}/opt/${PORTNAME}/ppds/Epson -type f -exec sed -i ""
's/\/opt\/epson/\/compat\/linux\/opt\/epson/g' {} \;)
(cp -r ${WRKSRC}/opt/${PORTNAME} ${STAGEDIR}/${PORTNAME})
(cp -r ${STAGEDIR}/${PORTNAME} /compat/linux/opt/)
(ln -sf /compat/linux/opt/${PORTNAME}/ppds/Epson
/usr/local/share/cups/model/)
(touch ./pkg-plist)
(find /compat/linux/opt/${PORTNAME} > ./pkg-plist)
(echo '/usr/local/share/cups/model/Epson' >> ./pkg-plist)


make makeplist
===>  License GPLv2 accepted by the user
===>   epson-inkjet-printer-201401w-201401w_1 depends on file:
/usr/local/sbin/pkg - found
===> Fetching all distfiles required by
epson-inkjet-printer-201401w-201401w_1 for building
===>  Extracting for epson-inkjet-printer-201401w-201401w_1
=> SHA256 Checksum OK for
epson-inkjet-printer-201401w/201401w/epson-inkjet-printer-201401w-1.0.0-1lsb3.2.x86_64.rpm.
===>  Patching for epson-inkjet-printer-201401w-201401w_1
===>  Configuring for epson-inkjet-printer-201401w-201401w_1
===>  Staging for epson-inkjet-printer-201401w-201401w_1
===>   epson-inkjet-printer-201401w-201401w_1 depends on package:
linux-c6-cups-libs>0 - found
===>   epson-inkjet-printer-201401w-201401w_1 depends on package:
linux-c6-jpeg>0 - found
===>   Generating temporary packing list
(gunzip
/usr/ports/print/epson-inkjet-printer-201401w/work/epson-inkjet-printer-201401w-201401w_1/opt/epson-inkjet-printer-201401w/ppds/Epson/*)
(find
/usr/ports/print/epson-inkjet-printer-201401w/work/epson-inkjet-printer-201401w-201401w_1/opt/epson-inkjet-printer-201401w/ppds/Epson
-type f -exec sed -i "" 's/\/opt\/epson/\/compat\/linux\/opt\/epson/g' {}
\;)
(cp -r
/usr/ports/print/epson-inkjet-printer-201401w/work/epson-inkjet-printer-201401w-201401w_1/opt/epson-inkjet-printer-201401w
/usr/ports/print/epson-inkjet-printer-201401w/work/stage/epson-inkjet-printer-201401w)
(cp -r
/usr/ports/print/epson-inkjet-printer-201401w/work/stage/epson-inkjet-printer-201401w
/compat/linux/opt/)
(ln -sf /compat/linux/opt/epson-inkjet-printer-201401w/ppds/Epson
/usr/local/share/cups/model/)
(touch ./pkg-plist)
(find /compat/linux/opt/epson-inkjet-printer-201401w > ./pkg-plist)
(echo '/usr/local/share/cups/model/Epson' >> ./pkg-plist)
> Compressing man pages (compress-man)
> Running Q/A tests (stage-qa)
Warning:
'/usr/ports/print/epson-inkjet-printer-201401w/work/stage/epson-inkjet-printer-201401w/lib64/libEpson_201401w.so.1.0.0'
is not stripped consider trying INSTALL_TARGET=install-strip or using
${STRIP_CMD}
Warning:
'/usr/ports/print/epson-inkjet-printer-201401w/work/stage/epson-inkjet-printer-201401w/lib64/libEpson_201401w.MT.so.1.0.0'
is not stripped consider trying INSTALL_TARGET=install-strip or using
${STRIP_CMD}
Warning:
'/usr/ports/print/epson-inkjet-printer-201401w/work/stage/epson-inkjet-printer-201401w/cups/lib/filter/epson_inkjet_printer_filter'
is not stripped consider trying INSTALL_TARGET=install-strip or using
${STRIP_CMD}
/you/have/to/check/what/makeplist/gives/you
/epson-inkjet-printer-201401w/cups/lib/filter/epson_inkjet_printer_filter
/epson-inkjet-printer-201401w/doc/AUTHORS
/epson-inkjet-printer-201401w/doc/COPYING
/epson-inkjet-printer-201401w/doc/COPYING.EPSON
/epson-inkjet-printer-201401w/doc/COPYING.LIB
/epson-inkjet-printer-201401w/doc/Manual.txt
/epson-inkjet-printer-201401w/doc/README
/epson-inkjet-printer-201401w/lib64/libEpson_201401w.MT.so.1.0.0
/epson-inkjet-printer-201401w/lib64/libEpson_201401w.so.1.0.0
/epson-inkjet-printer-201401w/ppds/Epson/Epson-L130_Series-epson-driver.ppd
/epson-inkjet-printer-201401w/ppds/Epson/Epson-L132_Series-epson-driver.ppd
/epson-inkjet-printer-201401w/ppds/Epson/Epson-L220_Series-epson-driver.ppd
/epson-inkjet-printer-201401w/ppds/Epson/Epson-L222_Series-epson-driver.ppd
/epson-inkjet-printer-201401w/ppds/Epson/Epson-L310_Series-epson-driver.ppd
/epson-inkjet-printer-201401w/ppds/Epson/Epson-L312_Series-epson-driver.ppd
/epson-inkjet-printer-201401w/ppds/Epson/Epson-L360_Series-epson-driver.ppd
/epson-inkjet-printer-201401w/ppds/Epson/Epson-L362_Series-epson-driver.ppd
/epson-inkjet-printer-201401w/ppds/Epson/Epson-L365_Series-epson-driver.ppd
/epson-inkjet-printer-201401w/ppds/Epson/Epson-L366_Series-epson-driver.ppd
/epson-inkjet-printer-201401w/ppds/Epson/Epson-L455_Series-epson-driver.ppd
/epson-inkjet-printer-201401w/ppds/Epson/Epson-L456_Series-epson-driver.ppd
/epson-inkjet-printer-201401w/resource/Epson_201401w.1.data
/epson-inkjet-printer-201401w/resource/Epson_201401w.MT.1.data
/epson-inkjet-printer-201401w/resource/Epson_201401w.MT.2.data
/epson-inkjet-printer-201401w/resource/Epson_201401w.MT.3.data
/epson-inkjet-printer-201401w/resource/Epson_201401w.MT.4.data

Re: Making port check-plist errors

[Jov]

Hi
 you should use 'make makeplist' to generate pkg-plist file. make
check-plist to verify to pkg-plist after make.

2017-07-12 13:46 GMT+08:00 blubee blubeeme :

> I am running into errors when trying to register the installation files.
>
> The Makefile is pretty barebones, it looks like this so far:
> PORTNAME=epson-inkjet-printer-201401w
> PORTVERSION=201401w
> PORTREVISION=1
> PORTEPOCH=0
> CATEGORIES=print
> MASTER_SITES=  https://download3.ebz.epson.net/dsc/f/03/00/03/45/41/
> d95c03482376873661d7a8d4c165b385cd082cf3/:amd64 \
>https://download3.ebz.epson.net/dsc/f/03/00/03/45/41/
> 0c527f1eef727e350302db951a45d31319ee501b/:i386
>
> DISTFILES_amd64=   epson-inkjet-printer-201401w-
> 1.0.0-1lsb3.2.x86_64.rpm:amd64
> DISTFILES_i386=epson-inkjet-printer-201401w-
> 1.0.0-1lsb3.2.i486.rpm:i386
>
>
> LICENSE=LGPLv21
> DIST_SUBDIR=${PORTNAME}/${PORTVERSION}
>
> MAINTAINER=he...@blubee.me
> COMMENT=CUPS filter for Seiko Epson Color Ink Jet Printers
>
> RESTRICTED=GNU Lesser General Public License version 2.1. \
>This program links the following object codes  \
>which are distributed under the conditions of  \
>SEIKO EPSON CORPORATION SOFTWARE LICENSE AGREEMENT. \
>*libEpson_201401w.so.1.0.0 \
>*libEpson_201401w.MT.so.1.0.0
>
>
> NO_BUILD=yes
> NO_WRKSUBDIR=yes
> PLIST_SUB=LINUXBASE=${LINUXBASE}
> USES=linux
> USE_LINUX=cups-libs jpeg
>
> do-install:
> (echo ${WRKSRC})
> (gunzip ${WRKSRC}/opt/${PORTNAME}/ppds/Epson/*)
> (find ${WRKSRC}/opt/${PORTNAME}/ppds/Epson -type f -exec sed -i ""
> 's/\/opt\/epson/\/compat\/linux\/opt\/epson/g' {} \;)
> (cp -r ${WRKSRC}/opt/${PORTNAME} /compat/linux/opt/)
> (ln -sf /compat/linux/opt/${PORTNAME}/ppds/Epson
> /usr/local/share/cups/model/)
> (touch ./pkg-plist)
> (find /compat/linux/opt/${PORTNAME} > ./pkg-plist)
> (echo '/usr/local/share/cups/model/Epson' >> ./pkg-plist)
>
> this is what the pkg-plist file looks like after that running make
> makeplist
>
> cat ./pkg-plist
> /compat/linux/opt/epson-inkjet-printer-201401w
> /compat/linux/opt/epson-inkjet-printer-201401w/cups
> /compat/linux/opt/epson-inkjet-printer-201401w/cups/lib
> /compat/linux/opt/epson-inkjet-printer-201401w/cups/lib/filter
> /compat/linux/opt/epson-inkjet-printer-201401w/cups/
> lib/filter/epson_inkjet_
> printer_filter
> /compat/linux/opt/epson-inkjet-printer-201401w/lib64
> /compat/linux/opt/epson-inkjet-printer-201401w/lib64/
> libEpson_201401w.so.1.0.0
> /compat/linux/opt/epson-inkjet-printer-201401w/lib64/
> libEpson_201401w.MT.so.1.0.0
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/Epson
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/
> Epson/Epson-L222_Series-epson-driver.ppd
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/
> Epson/Epson-L456_Series-epson-driver.ppd
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/
> Epson/Epson-L132_Series-epson-driver.ppd
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/
> Epson/Epson-L360_Series-epson-driver.ppd
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/
> Epson/Epson-L455_Series-epson-driver.ppd
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/
> Epson/Epson-L310_Series-epson-driver.ppd
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/
> Epson/Epson-L366_Series-epson-driver.ppd
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/
> Epson/Epson-L362_Series-epson-driver.ppd
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/
> Epson/Epson-L312_Series-epson-driver.ppd
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/
> Epson/Epson-L365_Series-epson-driver.ppd
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/
> Epson/Epson-L220_Series-epson-driver.ppd
> /compat/linux/opt/epson-inkjet-printer-201401w/ppds/
> Epson/Epson-L130_Series-epson-driver.ppd
> /compat/linux/opt/epson-inkjet-printer-201401w/doc
> /compat/linux/opt/epson-inkjet-printer-201401w/doc/README
> /compat/linux/opt/epson-inkjet-printer-201401w/doc/Manual.txt
> /compat/linux/opt/epson-inkjet-printer-201401w/doc/COPYING.EPSON
> /compat/linux/opt/epson-inkjet-printer-201401w/doc/COPYING.LIB
> /compat/linux/opt/epson-inkjet-printer-201401w/doc/COPYING
> /compat/linux/opt/epson-inkjet-printer-201401w/doc/AUTHORS
> /compat/linux/opt/epson-inkjet-printer-201401w/watermark
> /compat/linux/opt/epson-inkjet-printer-201401w/watermark/WEPCG07.EID
> /compat/linux/opt/epson-inkjet-printer-201401w/watermark/WEPCG00.EID
> /compat/linux/opt/epson-inkjet-printer-201401w/watermark/WEPCG09.EID
> /compat/linux/opt/epson-inkjet-printer-201401w/watermark/WEPCG08.EID
> /compat/linux/opt/epson-inkjet-printer-201401w/watermark/WEPCG01.EID
> /compat/linux/opt/epson-inkjet-printer-201401w/watermark/WEPCG06.EID
> /compat/linux/opt/epson-inkjet-printer-201401w/watermark/WEPCG05.EID
>