Re: NEW: net/vf1

2018-12-18 Thread Solene Rapenne
Edd Barrett wrote: > On Fri, Dec 14, 2018 at 06:13:02PM +0100, Paco Esteban wrote: > > Applied, here's the tar attached for convenience. > > Anyone willing to OK Paco's port? ok solene@ :) you can import

Re: NEW: net/vf1

2018-12-18 Thread Edd Barrett
On Fri, Dec 14, 2018 at 06:13:02PM +0100, Paco Esteban wrote: > Applied, here's the tar attached for convenience. Anyone willing to OK Paco's port? -- Best Regards Edd Barrett http://www.theunixzoo.co.uk

Re: NEW: net/vf1

2018-12-14 Thread Paco Esteban
On Fri, 14 Dec 2018, Edd Barrett wrote: > I think we can make the README more concise, like this: > > --- README.orig Fri Dec 14 16:48:13 2018 > +++ README Fri Dec 14 16:49:45 2018 > @@ -4,6 +4,5 @@ > | Running ${PKGSTEM} on OpenBSD > +--

Re: NEW: net/vf1

2018-12-14 Thread Edd Barrett
On Fri, Dec 14, 2018 at 05:31:47PM +0100, Paco Esteban wrote: > Find attached the port with the README instead of a patch. Good. I think we can make the README more concise, like this: --- README.orig Fri Dec 14 16:48:13 2018 +++ README Fri Dec 14 16:49:45 2018 @@ -4,6 +4,5 @@ | Running ${

Re: NEW: net/vf1

2018-12-14 Thread Paco Esteban
On Fri, 14 Dec 2018, Edd Barrett wrote: > Do we know if this is an OpenBSD-specific issue? As far as I know, yes. At least I could not reproduce it on a linux box I have here unsetting LC_* > If it is, or if we are not sure, I suggest adding that message instead > to a package README that gets i

Re: NEW: net/vf1

2018-12-14 Thread Edd Barrett
On Thu, Dec 13, 2018 at 06:52:14PM +0100, Paco Esteban wrote: > I guess a note on the README is enough. Here's the port with a patch for > that. If you think something else should be done, I can maybe contact > with the author. We've talked a couple of times on IRC and is a nice > guy. Do we know

Re: NEW: net/vf1

2018-12-13 Thread Paco Esteban
On Thu, 13 Dec 2018, Edd Barrett wrote: > On Thu, Dec 13, 2018 at 02:27:17PM +0100, Paco Esteban wrote: > > So, given this, should I make it dependent on textproc/py-chardet ? or > > should be enough with the "set this on your rc file" thing ? > > chardet makes no difference, however, setting LC_

Re: NEW: net/vf1

2018-12-13 Thread Edd Barrett
On Thu, Dec 13, 2018 at 02:27:17PM +0100, Paco Esteban wrote: > So, given this, should I make it dependent on textproc/py-chardet ? or > should be enough with the "set this on your rc file" thing ? chardet makes no difference, however, setting LC_CTYPE=en_US.UTF-8 makes the crash go away. Not sur

Re: NEW: net/vf1

2018-12-13 Thread Paco Esteban
Hi Edd, On Thu, 13 Dec 2018, Edd Barrett wrote: > Port-wise, I have one comment. I'd remove NO_TEST=Yes. Although there are no > tests, it still succeeds to invoke the test target. If tests are added in a > later release, we will run them without having to flip NO_TEST. Ok, I'll remove it. > I

Re: NEW: net/vf1

2018-12-13 Thread Edd Barrett
Hey Paco, On Thu, Dec 13, 2018 at 12:01:12PM +0100, Paco Esteban wrote: > Thanks Solène for your suggestion. > Here's the updated port. Port-wise, I have one comment. I'd remove NO_TEST=Yes. Although there are no tests, it still succeeds to invoke the test target. If tests are added in a later re

Re: NEW: net/vf1

2018-12-13 Thread Paco Esteban
On Thu, 13 Dec 2018, Solene Rapenne wrote: > Paco Esteban wrote: > > Ping. > > > > (zip attached again) > > hi > > the port looks fine to me but it doesn't provide any documentation. In the > sources there is a README.md file which could be used. You can use the port > sysutils/boar as an exam

Re: NEW: net/vf1

2018-12-12 Thread Solene Rapenne
Paco Esteban wrote: > Ping. > > (zip attached again) hi the port looks fine to me but it doesn't provide any documentation. In the sources there is a README.md file which could be used. You can use the port sysutils/boar as an example for adding the README.md file to the package.

Re: NEW: net/vf1

2018-12-12 Thread Paco Esteban
Ping. (zip attached again) -- Paco Esteban https://onna.be/gpgkey.asc vf1.tgz Description: Binary data

Re: NEW: net/vf1

2018-11-13 Thread Paco Esteban
On Tue, 13 Nov 2018, Stuart Henderson wrote: > I guess not too much interest in the 90's protocol from Minneapolis ;) Yeah, I can't blame anybody for that. It's almost archeology :-P > Anyway you sent the package, not the port. And that's the facepalm moment I was expecting ... Hopefully I'll

Re: NEW: net/vf1

2018-11-13 Thread Stuart Henderson
On 2018/11/13 20:07, Paco Esteban wrote: > On Wed, 07 Nov 2018, Paco Esteban wrote: > > > ping ... > > I guess there's no interest in this port. > > Anyway, could somebody please take a look at it just to tell me if > there's something wrong and/or what can I improve for future reference ? > >

Re: NEW: net/vf1

2018-11-13 Thread Paco Esteban
On Wed, 07 Nov 2018, Paco Esteban wrote: > ping ... I guess there's no interest in this port. Anyway, could somebody please take a look at it just to tell me if there's something wrong and/or what can I improve for future reference ? Thank you. -- Paco Esteban https://onna.be/gpgkey.asc

Re: NEW: net/vf1

2018-11-07 Thread Paco Esteban
ping ... On Tue, 30 Oct 2018, Paco Esteban wrote: > Hi all, > > Find attached vf1-0.0.10. > This is a small gopher client written in python I usually use (not > written by me though). > > - > $ pkg_info vf1 > Information for inst:vf1-0.0.10 > > Comment: > command line gopher client > > De

NEW: net/vf1

2018-10-30 Thread Paco Esteban
Hi all, Find attached vf1-0.0.10. This is a small gopher client written in python I usually use (not written by me though). - $ pkg_info vf1 Information for inst:vf1-0.0.10 Comment: command line gopher client Description: VF-1 is a command line gopher client. It is built around an interacti