Re: [new] net/i2pd 2.25.0

2019-06-15 Thread Mikal Villa

Hi,

Thanks for your reply and OK Rafael! I've updated with sthen@'s changes,
however I have also updated the port to don't have the need for cmake,
and it now install client application headers and the static libraries
needed from i2pd to build a client app. Thus, I also removed the test he
added but I think this flavor is better (less dependencies versus test).
i2pd has a few unit tests but I can ensure you that Orignal the main dev
will not put of time for some tests at least not this year.

Regarding the cmake and why it was there, the reason for this was that I
took the "less broken" attempt to port i2pd to OpenBSD and changed it
just to get started into the ports system.
However, gotten far much better known with the ports system now I decided
to try without it, since I recalled we had a Makefile.bsd and which was
still working great.

Also I noticed I didn't get my thunderbird to work with the text and line
breaks in the mailing list, so this would be my first neomutt/mutt email
ever. So I'll resend and fixup my mistakes like, if I for example 
messes up with the attachment.

Hopefully I don't bug you all with the horrible line breaks anymore :)



/Mikal


On 15/06/2019, 12:04, Rafael Sadowski wrote:

Please find attached a new tarball based on sthen@ work which fix the
test build.

Since there have been a lot of requests for this port and this one looks
fine for me. OK rsadowski@

On Thu Jun 13, 2019 at 06:19:33AM +0200, Mikal Villa wrote:

Hi,

Thanks a lot for your reply and corrections of the port. And yea, you're
probably right about
giving it a small description, I was way to focused about just trying to
get the port as correct
as possible that it didn't even occur to me.

So, what is it and why should you care?

I2P is short for Invisible Internet Project and it's a mix-network with
many similarities with the Tor network.
However some main differences is that instead of using centralized
directory servers which Tor does, I2P
has it's own DHT network, and routers have to learn themself which are
good relays and not. So Tor has a
faster bootup, but I2P is fully decentralizd. Both project where started
up ~16-17 years ago, however I2P
is much less known than Tor, and while Tor has had much focus on
out-proxying back to the internet, I2P
has had focus on hidden services and applications inside the network
which never leaves back to the internet.
I2P also has a very simple naming system, so you can have addresses like
planet.i2p and stats.i2p instead of
something similar to ouad893ou4fj09fe0f.onion. (Yes, that was just me
baning on the keyboard)


Again, thanks a lot for your tip and corrections of the port Stuart!


Best regards,
Mikal Villa


On 11/06/2019 13:42, Stuart Henderson wrote:
> On 2019/06/11 10:27, Mikal Villa wrote:
>> Hi,
>>
>> Since my first request the 2.26.0 release was done so I've also updated
>> the port.
>>
>> Can't seem to have gotten any replies on it, is there nobody that has
>> time to help me verify & import to cvs?
>>
>> I've attached the updated port.
>>
>>
>>
>> Best regards,
>> Mikal Villa
>>
>> On 06/06/2019 12:00, Mikal Villa wrote:
>>> Hi,
>>>
>>> This would be my first port, but I've actually read the documentation
>>> and think I got it right. Not totally sure about the PLIST but hopefully
>>> someone can point out my mistakes.
>>>
>>> I plan to update the i2pd source for OpenBSD so this port can lose it's
>>> current patch, but since the release was made before the port was
>>> written it's needed for now. This can be considered as a official port
>>> from the project.
>>>
>>> I don't have CVS access so I would need someone here to actually submit it.
>>>
>>>
>>> Best regards,
>>> Mikal Villa / Meeh
>>>
> It often helps a bit to describe the port in the email so readers can
> see if they might be interested in it.
>
> Updated tar attached with some cleanup, which I'll explain inline with the
> diff below. It is in better shape like this but I don't particularly want
> to run it for further tests so will leave it to someone else to pick up
> if they're interested.
>
>
> : diff --git a/Makefile b/Makefile
> : index 4ac5ff7..984070d 100755
> : --- a/Makefile
> : +++ b/Makefile
> : @@ -1,48 +1,42 @@
> :  # $OpenBSD$
> :
> : -GH_ACCOUNT =PurpleI2P
> : -GH_PROJECT =i2pd
> : -GH_TAGNAME =2.26.0
> : -DISTNAME =  i2pd-${GH_TAGNAME}
> : +COMMENT =   client for the I2P anonymous network
> : +
> : +GH_ACCOUNT =PurpleI2P
> : +GH_PROJECT =i2pd
> : +GH_TAGNAME =2.26.0
>
> spaces->tabs
> DISTNAME is set to $GH_PROJECT-$GH_TAGNAME by default, no need to set it 
separately
>
> : +
> :  CATEGORIES =net
> :  HOMEPAGE =  https://i2pd.website
> : -COMMENT =   full-featured C++ inplementation of a I2P router
>
> move up to standard position (see Makefile.template), reword a bit
> (keeping COMMENT simple, describing in DESCR)
>
> :
> :  MAINTAINER =Mikal Villa 
> :
> : -# BSD 3-clause
> : +# BSD
>
> standard in ports tree
>
> : 

Re: [new] net/i2pd 2.25.0

2019-06-15 Thread Rafael Sadowski
Please find attached a new tarball based on sthen@ work which fix the
test build.

Since there have been a lot of requests for this port and this one looks
fine for me. OK rsadowski@

On Thu Jun 13, 2019 at 06:19:33AM +0200, Mikal Villa wrote:
> Hi,
> 
> Thanks a lot for your reply and corrections of the port. And yea, you're
> probably right about
> giving it a small description, I was way to focused about just trying to
> get the port as correct
> as possible that it didn't even occur to me.
> 
> So, what is it and why should you care?
> 
> I2P is short for Invisible Internet Project and it's a mix-network with
> many similarities with the Tor network.
> However some main differences is that instead of using centralized
> directory servers which Tor does, I2P
> has it's own DHT network, and routers have to learn themself which are
> good relays and not. So Tor has a
> faster bootup, but I2P is fully decentralizd. Both project where started
> up ~16-17 years ago, however I2P
> is much less known than Tor, and while Tor has had much focus on
> out-proxying back to the internet, I2P
> has had focus on hidden services and applications inside the network
> which never leaves back to the internet.
> I2P also has a very simple naming system, so you can have addresses like
> planet.i2p and stats.i2p instead of
> something similar to ouad893ou4fj09fe0f.onion. (Yes, that was just me
> baning on the keyboard)
> 
> 
> Again, thanks a lot for your tip and corrections of the port Stuart!
> 
> 
> Best regards,
> Mikal Villa
> 
> 
> On 11/06/2019 13:42, Stuart Henderson wrote:
> > On 2019/06/11 10:27, Mikal Villa wrote:
> >> Hi,
> >>
> >> Since my first request the 2.26.0 release was done so I've also updated
> >> the port.
> >>
> >> Can't seem to have gotten any replies on it, is there nobody that has
> >> time to help me verify & import to cvs?
> >>
> >> I've attached the updated port.
> >>
> >>
> >>
> >> Best regards,
> >> Mikal Villa
> >>
> >> On 06/06/2019 12:00, Mikal Villa wrote:
> >>> Hi,
> >>>
> >>> This would be my first port, but I've actually read the documentation
> >>> and think I got it right. Not totally sure about the PLIST but hopefully
> >>> someone can point out my mistakes.
> >>>
> >>> I plan to update the i2pd source for OpenBSD so this port can lose it's
> >>> current patch, but since the release was made before the port was
> >>> written it's needed for now. This can be considered as a official port
> >>> from the project.
> >>>
> >>> I don't have CVS access so I would need someone here to actually submit 
> >>> it.
> >>>
> >>>
> >>> Best regards,
> >>> Mikal Villa / Meeh
> >>>
> > It often helps a bit to describe the port in the email so readers can
> > see if they might be interested in it.
> >
> > Updated tar attached with some cleanup, which I'll explain inline with the
> > diff below. It is in better shape like this but I don't particularly want
> > to run it for further tests so will leave it to someone else to pick up
> > if they're interested.
> >
> >
> > : diff --git a/Makefile b/Makefile
> > : index 4ac5ff7..984070d 100755
> > : --- a/Makefile
> > : +++ b/Makefile
> > : @@ -1,48 +1,42 @@
> > :  # $OpenBSD$
> > :  
> > : -GH_ACCOUNT =PurpleI2P
> > : -GH_PROJECT =i2pd
> > : -GH_TAGNAME =2.26.0
> > : -DISTNAME =   i2pd-${GH_TAGNAME}
> > : +COMMENT =client for the I2P anonymous network
> > : +
> > : +GH_ACCOUNT = PurpleI2P
> > : +GH_PROJECT = i2pd
> > : +GH_TAGNAME = 2.26.0
> >
> > spaces->tabs
> > DISTNAME is set to $GH_PROJECT-$GH_TAGNAME by default, no need to set it 
> > separately
> >
> > : +
> > :  CATEGORIES = net
> > :  HOMEPAGE =   https://i2pd.website
> > : -COMMENT =full-featured C++ inplementation of a I2P router
> >
> > move up to standard position (see Makefile.template), reword a bit
> > (keeping COMMENT simple, describing in DESCR)
> >
> > :  
> > :  MAINTAINER = Mikal Villa 
> > :  
> > : -# BSD 3-clause
> > : +# BSD
> >
> > standard in ports tree
> >
> > : -PERMIT_PACKAGE_CDROM =   Yes
> > : +PERMIT_PACKAGE = Yes
> >
> > this is gradually being replaced in the ports tree
> >
> > : +WANTLIB += ${COMPILER_LIBCXX} boost_date_time-mt boost_filesystem-mt
> > : +WANTLIB += boost_program_options-mt boost_system-mt c crypto m
> > : +WANTLIB += ssl z
> > :  
> > : -WANTLIB =${COMPILER_LIBCXX} boost_date_time boost_filesystem \
> > : - boost_program_options boost_system  c crypto m ssl z
> > : +COMPILER =   base-clang ports-gcc
> > : +MODULES =devel/cmake
> >
> > you already patch the cmake file, and it has an install target, and
> > installs the headers for the library, so might as well use it.
> >
> > :  LIB_DEPENDS =devel/boost
> > :  
> > : -COMPILER  =base-clang ports-gcc base-gcc
> >
> > boost needs a c++11 compiler already so no point having base-gcc in this 
> > list
> >
> > : -USE_GMAKE =  Yes
> > : -SUBST_VARS += VARBASE
> >
> > should use LOCALSTATEDIR which is already in 

Re: [new] net/i2pd 2.25.0

2019-06-12 Thread Mikal Villa
Hi,

Thanks a lot for your reply and corrections of the port. And yea, you're
probably right about
giving it a small description, I was way to focused about just trying to
get the port as correct
as possible that it didn't even occur to me.

So, what is it and why should you care?

I2P is short for Invisible Internet Project and it's a mix-network with
many similarities with the Tor network.
However some main differences is that instead of using centralized
directory servers which Tor does, I2P
has it's own DHT network, and routers have to learn themself which are
good relays and not. So Tor has a
faster bootup, but I2P is fully decentralizd. Both project where started
up ~16-17 years ago, however I2P
is much less known than Tor, and while Tor has had much focus on
out-proxying back to the internet, I2P
has had focus on hidden services and applications inside the network
which never leaves back to the internet.
I2P also has a very simple naming system, so you can have addresses like
planet.i2p and stats.i2p instead of
something similar to ouad893ou4fj09fe0f.onion. (Yes, that was just me
baning on the keyboard)


Again, thanks a lot for your tip and corrections of the port Stuart!


Best regards,
Mikal Villa


On 11/06/2019 13:42, Stuart Henderson wrote:
> On 2019/06/11 10:27, Mikal Villa wrote:
>> Hi,
>>
>> Since my first request the 2.26.0 release was done so I've also updated
>> the port.
>>
>> Can't seem to have gotten any replies on it, is there nobody that has
>> time to help me verify & import to cvs?
>>
>> I've attached the updated port.
>>
>>
>>
>> Best regards,
>> Mikal Villa
>>
>> On 06/06/2019 12:00, Mikal Villa wrote:
>>> Hi,
>>>
>>> This would be my first port, but I've actually read the documentation
>>> and think I got it right. Not totally sure about the PLIST but hopefully
>>> someone can point out my mistakes.
>>>
>>> I plan to update the i2pd source for OpenBSD so this port can lose it's
>>> current patch, but since the release was made before the port was
>>> written it's needed for now. This can be considered as a official port
>>> from the project.
>>>
>>> I don't have CVS access so I would need someone here to actually submit it.
>>>
>>>
>>> Best regards,
>>> Mikal Villa / Meeh
>>>
> It often helps a bit to describe the port in the email so readers can
> see if they might be interested in it.
>
> Updated tar attached with some cleanup, which I'll explain inline with the
> diff below. It is in better shape like this but I don't particularly want
> to run it for further tests so will leave it to someone else to pick up
> if they're interested.
>
>
> : diff --git a/Makefile b/Makefile
> : index 4ac5ff7..984070d 100755
> : --- a/Makefile
> : +++ b/Makefile
> : @@ -1,48 +1,42 @@
> :  # $OpenBSD$
> :  
> : -GH_ACCOUNT =PurpleI2P
> : -GH_PROJECT =i2pd
> : -GH_TAGNAME =2.26.0
> : -DISTNAME = i2pd-${GH_TAGNAME}
> : +COMMENT =  client for the I2P anonymous network
> : +
> : +GH_ACCOUNT =   PurpleI2P
> : +GH_PROJECT =   i2pd
> : +GH_TAGNAME =   2.26.0
>
> spaces->tabs
> DISTNAME is set to $GH_PROJECT-$GH_TAGNAME by default, no need to set it 
> separately
>
> : +
> :  CATEGORIES =   net
> :  HOMEPAGE = https://i2pd.website
> : -COMMENT =  full-featured C++ inplementation of a I2P router
>
> move up to standard position (see Makefile.template), reword a bit
> (keeping COMMENT simple, describing in DESCR)
>
> :  
> :  MAINTAINER =   Mikal Villa 
> :  
> : -# BSD 3-clause
> : +# BSD
>
> standard in ports tree
>
> : -PERMIT_PACKAGE_CDROM = Yes
> : +PERMIT_PACKAGE = Yes
>
> this is gradually being replaced in the ports tree
>
> : +WANTLIB += ${COMPILER_LIBCXX} boost_date_time-mt boost_filesystem-mt
> : +WANTLIB += boost_program_options-mt boost_system-mt c crypto m
> : +WANTLIB += ssl z
> :  
> : -WANTLIB =  ${COMPILER_LIBCXX} boost_date_time boost_filesystem \
> : -   boost_program_options boost_system  c crypto m ssl z
> : +COMPILER = base-clang ports-gcc
> : +MODULES =  devel/cmake
>
> you already patch the cmake file, and it has an install target, and
> installs the headers for the library, so might as well use it.
>
> :  LIB_DEPENDS =  devel/boost
> :  
> : -COMPILER  =base-clang ports-gcc base-gcc
>
> boost needs a c++11 compiler already so no point having base-gcc in this list
>
> : -USE_GMAKE =Yes
> : -SUBST_VARS += VARBASE
>
> should use LOCALSTATEDIR which is already in SUBST_VARS
>
> : -
> : -#FAKE_FLAGS= sysconfdir=${PREFIX}/share/examples
> : -
> : -# The upstream makefile has no install target.
> : -do-install:
> : -   ${INSTALL_PROGRAM} ${WRKSRC}/i2pd ${PREFIX}/sbin
> : -   ${INSTALL_DATA} ${WRKSRC}/libi2pd.a ${PREFIX}/lib
> : -   ${INSTALL_DATA} ${WRKSRC}/libi2pdclient.a ${PREFIX}/lib
> : +WRKSRC =   ${WRKDIST}/build
> :  
> :  post-install:
> : ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/i2pd/certificates/family
> : ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/i2pd/certificates/reseed
> : 

Re: [new] net/i2pd 2.25.0

2019-06-11 Thread Stuart Henderson
On 2019/06/11 10:27, Mikal Villa wrote:
> Hi,
> 
> Since my first request the 2.26.0 release was done so I've also updated
> the port.
> 
> Can't seem to have gotten any replies on it, is there nobody that has
> time to help me verify & import to cvs?
> 
> I've attached the updated port.
> 
> 
> 
> Best regards,
> Mikal Villa
> 
> On 06/06/2019 12:00, Mikal Villa wrote:
> > Hi,
> >
> > This would be my first port, but I've actually read the documentation
> > and think I got it right. Not totally sure about the PLIST but hopefully
> > someone can point out my mistakes.
> >
> > I plan to update the i2pd source for OpenBSD so this port can lose it's
> > current patch, but since the release was made before the port was
> > written it's needed for now. This can be considered as a official port
> > from the project.
> >
> > I don't have CVS access so I would need someone here to actually submit it.
> >
> >
> > Best regards,
> > Mikal Villa / Meeh
> >

It often helps a bit to describe the port in the email so readers can
see if they might be interested in it.

Updated tar attached with some cleanup, which I'll explain inline with the
diff below. It is in better shape like this but I don't particularly want
to run it for further tests so will leave it to someone else to pick up
if they're interested.


: diff --git a/Makefile b/Makefile
: index 4ac5ff7..984070d 100755
: --- a/Makefile
: +++ b/Makefile
: @@ -1,48 +1,42 @@
:  # $OpenBSD$
:  
: -GH_ACCOUNT =PurpleI2P
: -GH_PROJECT =i2pd
: -GH_TAGNAME =2.26.0
: -DISTNAME =   i2pd-${GH_TAGNAME}
: +COMMENT =client for the I2P anonymous network
: +
: +GH_ACCOUNT = PurpleI2P
: +GH_PROJECT = i2pd
: +GH_TAGNAME = 2.26.0

spaces->tabs
DISTNAME is set to $GH_PROJECT-$GH_TAGNAME by default, no need to set it 
separately

: +
:  CATEGORIES = net
:  HOMEPAGE =   https://i2pd.website
: -COMMENT =full-featured C++ inplementation of a I2P router

move up to standard position (see Makefile.template), reword a bit
(keeping COMMENT simple, describing in DESCR)

:  
:  MAINTAINER = Mikal Villa 
:  
: -# BSD 3-clause
: +# BSD

standard in ports tree

: -PERMIT_PACKAGE_CDROM =   Yes
: +PERMIT_PACKAGE = Yes

this is gradually being replaced in the ports tree

: +WANTLIB += ${COMPILER_LIBCXX} boost_date_time-mt boost_filesystem-mt
: +WANTLIB += boost_program_options-mt boost_system-mt c crypto m
: +WANTLIB += ssl z
:  
: -WANTLIB =${COMPILER_LIBCXX} boost_date_time boost_filesystem \
: - boost_program_options boost_system  c crypto m ssl z
: +COMPILER =   base-clang ports-gcc
: +MODULES =devel/cmake

you already patch the cmake file, and it has an install target, and
installs the headers for the library, so might as well use it.

:  LIB_DEPENDS =devel/boost
:  
: -COMPILER  =base-clang ports-gcc base-gcc

boost needs a c++11 compiler already so no point having base-gcc in this list

: -USE_GMAKE =  Yes
: -SUBST_VARS += VARBASE

should use LOCALSTATEDIR which is already in SUBST_VARS

: -
: -#FAKE_FLAGS= sysconfdir=${PREFIX}/share/examples
: -
: -# The upstream makefile has no install target.
: -do-install:
: - ${INSTALL_PROGRAM} ${WRKSRC}/i2pd ${PREFIX}/sbin
: - ${INSTALL_DATA} ${WRKSRC}/libi2pd.a ${PREFIX}/lib
: - ${INSTALL_DATA} ${WRKSRC}/libi2pdclient.a ${PREFIX}/lib
: +WRKSRC = ${WRKDIST}/build
:  
:  post-install:
:   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/i2pd/certificates/family
:   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/i2pd/certificates/reseed
:   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/i2pd/certificates/router
: - ${INSTALL_DATA} ${WRKSRC}/contrib/certificates/family/* \
: + ${INSTALL_DATA} ${WRKDIST}/contrib/certificates/family/* \


setting WRKSRC to a subdirectory to use the cmake infrastructure means that
these dirs need changing

i also added a do-test target in the attached file but haven't updated the
diff; however it fails

:  .include 
: diff --git a/patches/patch-build_CMakeLists_txt 
b/patches/patch-build_CMakeLists_txt
: index de3e6e1..5db3b5c 100644
: --- a/patches/patch-build_CMakeLists_txt
: +++ b/patches/patch-build_CMakeLists_txt
: @@ -1,7 +1,8 @@
:  build/CMakeLists.txt.origFri Nov  9 05:22:55 2018
: -+++ build/CMakeLists.txt Tue Nov 13 21:08:17 2018
: -@@ -471,7 +471,7 @@
: -   endif()
: +Index: build/CMakeLists.txt
: +--- build/CMakeLists.txt.orig
:  build/CMakeLists.txt
: +@@ -473,7 +473,7 @@ if (WITH_BINARY)
: +   target_link_libraries(libi2pd ${Boost_LIBRARIES} ${ZLIB_LIBRARY})
: target_link_libraries( "${PROJECT_NAME}" libi2pd libi2pdclient ${DL_LIB} 
${Boost_LIBRARIES} ${OPENSSL_LIBRARIES} ${ZLIB_LIBRARY} 
${CMAKE_THREAD_LIBS_INIT} ${MINGW_EXTRA} ${DL_LIB} ${CMAKE_REQUIRED_LIBRARIES})
:   
:  -  install(TARGETS "${PROJECT_NAME}" RUNTIME DESTINATION 
${CMAKE_INSTALL_BINDIR} COMPONENT Runtime)
: @@ -9,7 +10,7 @@
: set (APPS 
"\${CMAKE_INSTALL_PREFIX}/bin/${PROJECT_NAME}${CMAKE_EXECUTABLE_SUFFIX}")
: set (DIRS 

Re: [new] net/i2pd 2.25.0

2019-06-11 Thread Mikal Villa
Hi,

Since my first request the 2.26.0 release was done so I've also updated
the port.

Can't seem to have gotten any replies on it, is there nobody that has
time to help me verify & import to cvs?

I've attached the updated port.



Best regards,
Mikal Villa

On 06/06/2019 12:00, Mikal Villa wrote:
> Hi,
>
> This would be my first port, but I've actually read the documentation
> and think I got it right. Not totally sure about the PLIST but hopefully
> someone can point out my mistakes.
>
> I plan to update the i2pd source for OpenBSD so this port can lose it's
> current patch, but since the release was made before the port was
> written it's needed for now. This can be considered as a official port
> from the project.
>
> I don't have CVS access so I would need someone here to actually submit it.
>
>
> Best regards,
> Mikal Villa / Meeh
>


net-i2pd-2.26.tar.bz2
Description: BZip2 compressed data


[new] net/i2pd 2.25.0

2019-06-06 Thread Mikal Villa
Hi,

This would be my first port, but I've actually read the documentation
and think I got it right. Not totally sure about the PLIST but hopefully
someone can point out my mistakes.

I plan to update the i2pd source for OpenBSD so this port can lose it's
current patch, but since the release was made before the port was
written it's needed for now. This can be considered as a official port
from the project.

I don't have CVS access so I would need someone here to actually submit it.


Best regards,
Mikal Villa / Meeh



net-i2pd.tar.bz2
Description: BZip2 compressed data


Re: [NEW] net/i2pd

2017-12-28 Thread Klemens Nanni
On Thu, Dec 28, 2017 at 02:47:34PM +0100, Rubén Llorente wrote:
> * Version bumped to 2.17.0
> * Some old family and reseed certificates removed.
Good.

> * DISTFILE/WORKDIST/GH_* workarounds have been fixed.
It's GH_TAGNAME not GH_TAG and portcheck(1) does throw errors. With GH_*
there's no need for V, DISTNAME or DISTFILES at all.

> * Added README with comments regarding openfile limits.
> * Added a NO_TEST = Yes line.
i2pd has tests and you should use them.

> * Moved devel/boost to LIB_DEPEND only
I added the minimal requirements version.

> * Moved everything in post-install into do-install
That's good. I took the liberty to squash them a little further, what do
you say?

> Have fun testing the hell out of this.
 $ mk test
 ===>  Regression tests for i2pd-2.17.0
 gmake -C /usr/obj/ports/i2pd-2.17.0/i2pd-2.17.0/tests
 gmake: Entering directory 
'/usr/obj/ports/i2pd-2.17.0/i2pd-2.17.0/tests'
 g++ -Wall -Wextra -pedantic -O0 -g -std=c++11 
-D_GLIBCXX_USE_NANOSLEEP=1 -I../libi2pd/ -pthread   -o test-gost-sig 
../libi2pd/Gost.cpp ../libi2pd/I2PEndian.cpp ../libi2pd/Signature.cpp 
../libi2pd/Crypto.cpp ../libi2pd/Log.cpp test-gost-sig.cpp -lcrypto -lssl 
-lboost_system
 cc1plus: error: unrecognized command line option "-std=c++11"
 cc1plus: error: unrecognized command line option "-std=c++11"
 cc1plus: error: unrecognized command line option "-std=c++11"
 cc1plus: error: unrecognized command line option "-std=c++11"
 cc1plus: error: unrecognized command line option "-std=c++11"
 cc1plus: error: unrecognized command line option "-std=c++11"
 gmake: *** [Makefile:17: test-gost-sig] Error 1
 gmake: Leaving directory '/usr/obj/ports/i2pd-2.17.0/i2pd-2.17.0/tests'
 *** Error 2 in . (Makefile:44 'do-test')
 *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2771 
'/usr/obj/ports/i2pd-2.17.0/.test_done')
 *** Error 1 in /usr/ports/net/i2pd 
(/usr/ports/infrastructure/mk/bsd.port.mk:2419 'test')

Tests need work, it's your turn again. I'd probably start with COMPILER
in bsd.port.mk(5) and work from there; hint: look at
https://i2pd.readthedocs.io/en/latest/devs/building/requirements/ .

The following diff applies to your latest tarball and incorporates my
feedback.

The order of variables throughout the Makefile is taken from
/usr/ports/infrastructure/templates/Makefile.template.

--- Makefile.orig   Thu Dec 28 14:40:13 2017
+++ MakefileThu Dec 28 21:06:44 2017
@@ -1,47 +1,46 @@
 # $OpenBSD$
 
-V =2.17.0
-DISTNAME = i2pd-${V}
-DISTFILES =i2pd-{}${V}${EXTRACT_SUFX}
+COMMENT =  C++ port of the i2p router
+
+GH_ACCOUNT =   PurpleI2P
+GH_PROJECT =   i2pd
+GH_TAGNAME =   2.17.0
+
 CATEGORIES =   net
+
 HOMEPAGE = http://i2pd.website
-COMMENT =  C++ port of the i2p router
 
 MAINTAINER =   Ruben Llorente 
 
 # BSD 3-clause
 PERMIT_PACKAGE_CDROM = Yes
 
-GH_ACCOUNT =   PurpleI2P
-GH_PROJECT =   i2pd
-GH_TAG =   ${V}
+WANTLIB += boost_date_time-mt boost_filesystem-mt
+WANTLIB += boost_program_options-mt boost_system-mt
+WANTLIB += ${COMPILER_LIBCXX} c crypto m ssl z
 
-WANTLIB =  ${COMPILER_LIBCXX} boost_date_time boost_filesystem \
-   boost_program_options boost_system  c crypto m ssl z
-LIB_DEPENDS =  devel/boost
+LIB_DEPENDS =  devel/boost>=1.49
 
 USE_GMAKE =Yes
 
-NO_TEST =  Yes
-
 SYSCONFDIR =   ${VARBASE}/i2pd/.i2pd/
 
 do-install:
${INSTALL_PROGRAM} ${WRKSRC}/i2pd ${PREFIX}/bin
-   ${INSTALL_DATA} ${WRKSRC}/libi2pd.a ${PREFIX}/lib
-   ${INSTALL_DATA} ${WRKSRC}/libi2pdclient.a ${PREFIX}/lib
-   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/i2pd/certificates/family
-   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/i2pd/certificates/reseed
-   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/i2pd/certificates/router
-   ${INSTALL_DATA} ${WRKSRC}/contrib/certificates/family/* \
-   ${PREFIX}/share/examples/i2pd/certificates/family
-   ${INSTALL_DATA} ${WRKSRC}/contrib/certificates/reseed/* \
-   ${PREFIX}/share/examples/i2pd/certificates/reseed
-   ${INSTALL_DATA} ${WRKSRC}/contrib/certificates/router/* \
-   ${PREFIX}/share/examples/i2pd/certificates/router
-   ${INSTALL_DATA} ${WRKSRC}/contrib/i2pd.conf \
-   ${PREFIX}/share/examples/i2pd/i2pd.conf
-   ${INSTALL_DATA} ${WRKSRC}/contrib/tunnels.conf \
-   ${PREFIX}/share/examples/i2pd/tunnels.conf
+   ${INSTALL_DATA} ${WRKSRC}/libi2pd{,client}.a ${PREFIX}/lib
+
+.for _d in family reseed router
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/i2pd/certificates/${_d}
+   ${INSTALL_DATA} ${WRKSRC}/contrib/certificates/${_d}/* \
+${PREFIX}/share/examples/i2pd/certificates/${_d}
+.endfor
+
+.for _f in i2pd.conf tunnels.conf
+   ${INSTALL_DATA} ${WRKSRC}/contrib/${_f} \
+   

Re: [NEW] net/i2pd

2017-12-28 Thread Rubén Llorente
I forgot to attach the actual port in my last message, here it is.

On Thu, Dec 28, 2017 at 02:47:34PM +0100, Rubén Llorente wrote:
> Here is an updated version of the i2pd port.
> 
> * Version bumped to 2.17.0
> * Some old family and reseed certificates removed.
> * DISTFILE/WORKDIST/GH_* workarounds have been fixed.
> * Added README with comments regarding openfile limits.
> * Added a NO_TEST = Yes line.
> * Moved devel/boost to LIB_DEPEND only
> * Moved everything in post-install into do-install
> 
> Have fun testing the hell out of this.
> 
> -- 
> OpenPGP Key Fingerprint:
> BB5A C2A2 2CAD ACB7 D50D  C081 1DB9 6FC4 5AB7 92FA

-- 
OpenPGP Key Fingerprint:
BB5A C2A2 2CAD ACB7 D50D  C081 1DB9 6FC4 5AB7 92FA


i2pd.tar.gz
Description: application/tar-gz


Re: [NEW] net/i2pd

2017-12-28 Thread Rubén Llorente
Here is an updated version of the i2pd port.

* Version bumped to 2.17.0
* Some old family and reseed certificates removed.
* DISTFILE/WORKDIST/GH_* workarounds have been fixed.
* Added README with comments regarding openfile limits.
* Added a NO_TEST = Yes line.
* Moved devel/boost to LIB_DEPEND only
* Moved everything in post-install into do-install

Have fun testing the hell out of this.

-- 
OpenPGP Key Fingerprint:
BB5A C2A2 2CAD ACB7 D50D  C081 1DB9 6FC4 5AB7 92FA



Re: [NEW] net/i2pd

2017-12-24 Thread Stuart Henderson
On 2017/12/23 20:20, Klemens Nanni wrote:
> DISTNAME needs more than the version string, but you should use GH_*
> here anyway.

Yes. Single distfile using a github /archive/ url -> use GH_*.
(github /release/ URL -> use MASTER_SITES, multiple distfiles: it's
complicated. :) 



Re: [NEW] net/i2pd

2017-12-23 Thread Klemens Nanni
On Thu, Dec 14, 2017 at 12:29:55PM +0100, Rubén Llorente wrote:
> Here is a port I have been using locally. It is a non Java
> implementation of the i2p protocol. Maybe it will be useful for other
> OpenBSDers, so here you go.
> 
> Some comments and clarifications:
> 
> * Upstream's makefiles lack an "install" target. This is intended
> because upstream wants packagers to copy over their files manually.
> * i2pd gets installed as a poorman's system service with all its
> configuration on /var/i2pd. This folder gets pre-populated with config
> files provided by upstream. Trying to run the software without
> configuration files may cause it to run in a potentially insecure
> manner.
> * Upstream's config scripts are a bit messy and passing configuration
> parameters for the building process when using Clang is not possible.
> Since the defaults are sane enough, I think it is ok to let the port as
> it is.
> 
> Testing and destructive criticism ("get your hands off the keyboard
> before you get hurt, kid") are welcome.
A few things port wise from looking at your Makefile:

DISTNAME needs more than the version string, but you should use GH_*
here anyway.

bsd.port.mk(5) has all you need. If in doubt, look at other ports. Once
fixed, this will also remove the need for your WRKDIST workaround.

devel/boost belongs into LIB_DEPENDS only, again: see the manual.

Why post-install? One (big) do-install suffices. You can also drop the
comment, it's of no use imho.

Since NO_TEST is unset, what does `make test' say?

I suggest taking a look at the porting guide in our FAQ if you haven't
dont so already.


Thanks for your port,
I'm looking forward to it :)



[NEW] net/i2pd

2017-12-14 Thread Rubén Llorente
Here is a port I have been using locally. It is a non Java
implementation of the i2p protocol. Maybe it will be useful for other
OpenBSDers, so here you go.

Some comments and clarifications:

* Upstream's makefiles lack an "install" target. This is intended
because upstream wants packagers to copy over their files manually.
* i2pd gets installed as a poorman's system service with all its
configuration on /var/i2pd. This folder gets pre-populated with config
files provided by upstream. Trying to run the software without
configuration files may cause it to run in a potentially insecure
manner.
* Upstream's config scripts are a bit messy and passing configuration
parameters for the building process when using Clang is not possible.
Since the defaults are sane enough, I think it is ok to let the port as
it is.

Testing and destructive criticism ("get your hands off the keyboard
before you get hurt, kid") are welcome.

-- 
OpenPGP Key Fingerprint:
BB5A C2A2 2CAD ACB7 D50D  C081 1DB9 6FC4 5AB7 92FA


i2pd.tar
Description: Unix tar archive