Hi Giuseppe --

On 09/08/17 09:16, Giuseppe Cocomazzi wrote:
Hello,
what is the current status of this port? Will it be imported?

My patches have already been merged in the GNU APL current branch, so
OpenBSD will be "natively" supported from the next official GNU APL
release.

I am waiting for another developer to review the ports, and will import them once that has happened. Good to hear that all the patches have been merged upstream!

~Brian

Best,
Giuseppe Cocomazzi
http://sbudella.altervista.org


On Thu, Aug 17, 2017 at 11:11 AM, Giuseppe Cocomazzi <sbude...@gmail.com> wrote:
Yes, I renew my intention to be the maintainer of both ports. I have
also given notice about the ongoing porting effort to the GNU APL
maintainer, and I am willing to have the patches merged to their tree.
As for the security-oriented scrutiny I will try my best according to
my spare time.

In conclusion, from my side, since I use the interpreter daily for my
productivity, I would like to see it imported in our port collection.
Thank you very much.

On Thu, Aug 17, 2017 at 3:17 AM, Brian Callahan <bcal...@devio.us> wrote:
Hi --


On 07/21/17 14:50, Brian Callahan wrote:

On 7/21/2017 2:01 PM, Giuseppe Cocomazzi wrote:
Hi Brian, hi ports.

I think lang/apl is ready to be committed. It just needs a license
marker
tweak (it's just GPLv3+ now) and there's some trailing whitespace, but
that
can be fixed on import. ok for me.

Thanks a lot. My first port :)

I cleaned up the apl-fonts ports a bit, attached. Giuseppe, do you also
want
to be maintainer of the font/apl-fonts port?
Yes, no problem for me, I will preserve a copy of the fonts on my
homepage just in case the original webpage disappears at some point in
the future. Shall I add a line to $MASTER_SITES?
I don't think that's strictly necessary, but having an extra mirror
can't hurt.

Let me know if further actions from me are needed.
I think we're good. Have to wait on someone else's ok to import, though.

~Brian

Best,


Best,

On Fri, Jul 21, 2017 at 7:33 PM, Brian Callahan <bcal...@devio.us> wrote:
On 07/21/17 06:41, Giuseppe Cocomazzi wrote:
Alright, I made all the fixes and created a new port
for the APL fonts (apl-fonts), as suggested.

Find both ports attached.
I think lang/apl is ready to be committed. It just needs a license
marker
tweak (it's just GPLv3+ now) and there's some trailing whitespace, but
that
can be fixed on import. ok for me.

I cleaned up the apl-fonts ports a bit, attached. Giuseppe, do you also
want
to be maintainer of the font/apl-fonts port?

~Brian


Thanks.

On Thu, Jul 20, 2017 at 7:04 PM, Brian Callahan <bcal...@devio.us>
wrote:
Hi Giuseppe --

On 07/20/17 02:48, Giuseppe Cocomazzi wrote:
Hi ports,
following Brian's and Ian's suggestions, I updated the port of
GNU Apl to account for:
- A default configuration file which disables coloring and enables ^D
to quit the interpreter;
- Adrian Smith's standard APL385 font shipped with the package.

All it takes for the special characters to be correctly displayed is
a
UTF-8 LC_CTYPE (/etc/gnu-apl.d/keyboard1.txt should display an alien
keyboard layout if everything is fine).

Tested on -current from latest snapshot:

OpenBSD wretch.doom.loc 6.1 GENERIC#194 i386

As soon as the port is integrated in the tree I will communicate my
patches back to the author of the program for a better OpenBSD
support.

Thanks for the feedback.
After some discussion with sthen, it was suggested to make the font
its
own
port.
You can make this one have a RUN_DEPENDS on the new font port, as
indeed
the
APL interpreter is unusable without the font.

Also, the V=1.7 variable in the port Makefile can go away. It's only
ever
used in the DISTNAME line, so DISTNAME can just become
DISTNAME=apl-1.7

Also please re-run `make update-plist` as I discovered that it there
were
some entries added to the PLIST when I did that.

Thanks!

~Brian


Best,

On Wed, Jul 19, 2017 at 5:38 PM, Brian Callahan <bcal...@devio.us>
wrote:
On 7/19/2017 10:09 AM, Ian Darwin wrote:
On Wed, Jul 19, 2017 at 03:45:30PM +0200, Giuseppe Cocomazzi wrote:
I asked one of the distributors (Dyalog) of the APL385 font and he
kindly addressed me to the page of the original Adrian Smith's
font,
where it is explicitly mentioned that the font is in the public
domain:

http://www.apl385.com/fonts/index.htm

The readme for Emacs APL mode, at
https://github.com/lokedhs/gnu-apl-mode,
suggests to use GNU FreeFont, which is GPL'd. If you can't find
documentation
that your other font is PD or otherwise licensable, I'd use their
"Free" Font.
It seems that GNU FreeFont is already in the port tree, so we have
two
options here: either we add FreeFont as a dependency to the
package
(which is not, technically) or we ship the APL385 font with the
package,
or we preserve the distribution as it is and only add a
'README.openBSD'
to address the user to further resources, just like Emacs APL mode
did.
That's three, actually :-) But given that the 385 font is indeed
explicitly PD I
would probably just include it, unless anyone else wants to weigh
in?

You should probably mention that the font is PD in the license
comment.

Makes sense to me.

These are still sitting in my queue. OK to import them? Reattached for
convenience.

~Brian



--
Giuseppe Cocomazzi
My self is steam.

Reply via email to