@eyedeekay
&Irc2PGuest39119
&eche|on
&zzz
+Anomaly
+R4SAS
+RN
+RN_
+T3s|4
+dr|z3d
+hk
+orignal
+postman
+wodencafe
Arch
DeltaOreo
FreeRider
FreefallHeavens
Irc2PGuest59363
Irc2PGuest68122
Irc2PGuest83611
Irc2PGuest9535
Leopold_
Nausicaa
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
Soni
T3s|4_
T3s|4___
Teeed
aargh1
acetone_
anon4
b3t4f4c3
bak83
boonst
cumlord
dr4wd3
eyedeekay_bnc
glowie
hagen_
itsjustme
khb
not_bob_afk
poriori_
rapidash
shiver_
solidx66
u5657
w8rabbit
weko_
x74a6
zzz
welcome xsysx I hear you wanted to talk about BSD?
xsysx
hey thx
xsysx
the problem is, the port on freebsd for i2p is very outdated (version 0.9.48) so I tried to figure out to compile the current version 2.4.0 on freebsd
xsysx
RN told me its better to install it by the .jar file...
xsysx
so my question is, would it help in any way, if I overtake the maintainership for the port? I'm not a dev or something, just interested in both projects
zzz
we have very little contact, if any, with the "downstream" BSD ports
zzz
couldn't tell you who or how to do that, every distro has their own rules and processes
zzz
but we'd be happy to provide any support you need
zzz
I try to keep track of all downstreams in the chart at stats.i2p/cgi-bin/dashboard.cgi
xsysx
I already know how to do it, the installation was successful. I'm asking more fore the relevance to update the port, because freebsd users could also download the .jar from the website
zzz
click thru those links to try to figure out best practices
zzz
the all-in-one jar file installer is a nsis-like packaging; that probably isn't appropriate for a distro
zzz
but I'm no BSD expert
zzz
we can wait for RN to wake up and join the discussion
dr|z3d
the installer isn't really an issue, it can be deployed with an install script on BSD.
dr|z3d
and presumably because BSD isn't debian, there's no actual requirement to make the updates available via repos, can just supply them via console updates.
zzz
I would start with whatever is there now ports.freebsd.org/cgi/ports.cgi?query=i2p&stype=all
zzz
and update it to 2.4.0
zzz
before trying to reinvent anything
xsysx
yes I updated that port to 2.4.0, no reinvention
xsysx
it worked very well
zzz
email the maintainer or get permissions, however that works on bsd ports
xsysx
I will try that
xsysx
at first
zzz
the chart on the dashboard I update manually, I'm sure there's more downstreams on 2.4.0 by now