Re: WireGuard for FreeBSD

2018-05-21 Thread Jason A. Donenfeld 
On Tue, May 22, 2018 at 2:33 AM, Outback Dingo  wrote:
> to be honest, while it sounds nice, i for one would prefer to see a
> kernel module ported to FreeBSD instead of userland
> second to that, building a freebsd port of it is not all that hard,
> however that being said, it also needs to be accepted
> upstream and committed by a ports maintainer, while i can help with
> creating it, i still feel a kernel module is a better fit

I too would prefer this, and maybe at some point down the line I'll
put some real time and effort into porting WireGuard from the Linux
kernel to kFreeBSD. But it's not the case that it's "not that hard";
doing so will be a pretty serious undertaking. That's going to take a
lot of time. Until that day arrives, what you speak of doesn't exist.
What we have instead today is tons of hard work that's gone into
bringing a userspace implementation.

So please, don't derail the current efforts in favor of an effort that
doesn't even exist at the moment.
___
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: WireGuard for FreeBSD

2018-05-21 Thread Jason A. Donenfeld 
Hi Chris,

Wonderful! Feel free to poke me on IRC -- I'm zx2c4 in #wireguard on
Freenode -- if you need any pointers in real time.

Some odds and ends that might help: to have a tarball of the latest
git master, you can use these links:

https://git.zx2c4.com/WireGuard/snapshot/WireGuard-master.tar.xz
https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-master.tar.xz

In a few days these will be released:

https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.201805XX.tar.xz
https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-0.0.201805XX.tar.xz

If you want to try setting up a quick tunnel using `wg-quick(8)`, you
can use the demo server -- for testing purposes only; please don't use
this for anything real -- via this simple script:

https://git.zx2c4.com/WireGuard/plain/contrib/examples/ncat-client-server/client-quick.sh

After it's up, you can try pinging 192.168.4.1 or visiting that in your browser.

Looking forward,
Jason
___
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: WireGuard for FreeBSD

2018-05-21 Thread Chris H 

On Mon, 21 May 2018 23:35:45 +0200 "Jason A. Donenfeld"  said


[cross-posted to the WireGuard mailing list]

Hello FreeBSD Ports List,

I'm the author of WireGuard [1], a secure network tunnel protocol [2]
and a set of implementations of it. It was originally designed for the
Linux kernel, but we're now beginning to have implementations for
other platforms. Recently, parts of the Internet got excited [3] when
we put a Darwin version in Homebrew. The last few days Brian (CC'd)
and I have been working on getting an implementation running on
FreeBSD, and things are coming along pretty smoothly.

I'm not entirely familiar with the ports/pkg adding process, and so I
was hoping to find somebody who is part of the FreeBSD community to
adopt WireGuard and help maintain packages for it.

I'm in!
I'll start the necessary research now.
Any additional pointers, and such you think may be helpful are
greatly appreciated.

Thanks, Jason!

--Chris

We currently have
packages for many Linux distros [4], but FreeBSD will be the first
open source BSD project. There are two packages to add:

1. wireguard-tools, providing wg(8) and wg-quick(8)
Runtime dependencies: bash, wireguard-go
Buildtime dependencies: gmake, c compiler, libc
Build: gmake -C src/tools WITH_WGQUICK=yes
Install: gmake -C src/tools PREFIX=/usr/local install
URL template:
https://git.zx2c4.com/WireGuard/snapshot/WireGuard-VERSION.tar.xz

2. wireguard-go
Runtime dependencies: none
Buildtime dependencies: gmake, go
Build: export GOPATH=$(pwd)/gopath; go get -d; gmake
Install: gmake PREFIX=/usr/local install
URL template:
https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-VERSION.tar.xz

For reference, these two packages in Homebrew look like this:
https://github.com/Homebrew/homebrew-core/blob/master/Formula/wireguard-tools.rb
https://github.com/Homebrew/homebrew-core/blob/master/Formula/wireguard-go.rb

And for your horror, I've made a please-dont-pipe-like-that
copy-and-paste install script:
# curl https://xn--4db.cc/0BwTeeYe | sh

That script won't work as-is at the moment, since I haven't yet tagged
tarballs with FreeBSD support, but in the coming days, I'll tag one
that has this latest FreeBSD code in it. (In the meantime, you can run
`# curl https://xn--4db.cc/0BwTeeYe | sh /dev/stdin --master` to get
it from git master.) I was hoping that in the time between now and
then, we might find somebody willing and interested in packaging this
properly.

Does this sound fun to anyone?

Best regards,
Jason


[1] https://www.wireguard.com/
[2] https://www.wireguard.com/papers/wireguard.pdf
[3] http://latacora.singles/2018/05/16/there-will-be.html
[4] https://www.wireguard.com/install/
___
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"

WireGuard for FreeBSD

2018-05-21 Thread Jason A. Donenfeld 
[cross-posted to the WireGuard mailing list]

Hello FreeBSD Ports List,

I'm the author of WireGuard [1], a secure network tunnel protocol [2]
and a set of implementations of it. It was originally designed for the
Linux kernel, but we're now beginning to have implementations for
other platforms. Recently, parts of the Internet got excited [3] when
we put a Darwin version in Homebrew. The last few days Brian (CC'd)
and I have been working on getting an implementation running on
FreeBSD, and things are coming along pretty smoothly.

I'm not entirely familiar with the ports/pkg adding process, and so I
was hoping to find somebody who is part of the FreeBSD community to
adopt WireGuard and help maintain packages for it. We currently have
packages for many Linux distros [4], but FreeBSD will be the first
open source BSD project. There are two packages to add:

1. wireguard-tools, providing wg(8) and wg-quick(8)
Runtime dependencies: bash, wireguard-go
Buildtime dependencies: gmake, c compiler, libc
Build: gmake -C src/tools WITH_WGQUICK=yes
Install: gmake -C src/tools PREFIX=/usr/local install
URL template: https://git.zx2c4.com/WireGuard/snapshot/WireGuard-VERSION.tar.xz

2. wireguard-go
Runtime dependencies: none
Buildtime dependencies: gmake, go
Build: export GOPATH=$(pwd)/gopath; go get -d; gmake
Install: gmake PREFIX=/usr/local install
URL template: 
https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-VERSION.tar.xz

For reference, these two packages in Homebrew look like this:
https://github.com/Homebrew/homebrew-core/blob/master/Formula/wireguard-tools.rb
https://github.com/Homebrew/homebrew-core/blob/master/Formula/wireguard-go.rb

And for your horror, I've made a please-dont-pipe-like-that
copy-and-paste install script:
# curl https://xn--4db.cc/0BwTeeYe | sh

That script won't work as-is at the moment, since I haven't yet tagged
tarballs with FreeBSD support, but in the coming days, I'll tag one
that has this latest FreeBSD code in it. (In the meantime, you can run
`# curl https://xn--4db.cc/0BwTeeYe | sh /dev/stdin --master` to get
it from git master.) I was hoping that in the time between now and
then, we might find somebody willing and interested in packaging this
properly.

Does this sound fun to anyone?

Best regards,
Jason


[1] https://www.wireguard.com/
[2] https://www.wireguard.com/papers/wireguard.pdf
[3] http://latacora.singles/2018/05/16/there-will-be.html
[4] https://www.wireguard.com/install/
___
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: Should we Rust warnings suggesting adding work/stage/usr/local/bin to the PATH?

2018-05-21 Thread Luca Pizzamiglio 
Hi Mateusz,
I've no idea how, but it's obviously misleading and somehow wrong, we
should mute this message

Best regards,
Luca

On Thu, May 17, 2018 at 3:26 PM, Stefan Esser  wrote:

> Am 17.05.18 um 14:42 schrieb Mateusz Piotrowski:
> > Hello,
> >
> > When I build Rust packages I get warnings like this one:
> >
> >> warning: be sure to add `/usr/home/0mp/ports/games/
> genact/work/stage/usr/local/bin` to your PATH to be able to run the
> installed binaries
> >
> > It is not very helpful when building ports. Do you think that we should
> > try to mute it by default?
>
> I have seen such a message when building a Haskell based port, too.
>
> Seems there are more languages (or build systems) that perform such
> a check and emit a misleading warning ...
>
> 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"
>
___
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: www/joomla3 port installs from GitHub, why?

2018-05-21 Thread Dan Mahoney (Gushi) 

On Mon, 21 May 2018, Peter Pentchev wrote:


On Sun, May 20, 2018 at 04:49:34PM -0700, Dan Mahoney (Gushi) wrote:

On Sun, 20 May 2018, Per olof Ljungmark wrote:


On 05/20/18 21:15, Eugene Grosbein wrote:

21.05.2018 2:02, Per olof Ljungmark wrote:



OK, I'll try to explain a bit more.

Firstly, this port is PHP code and needs no compilation, so they are
both source files. NO_BUILD=   yes

www/wordpress is a similar port, correctly implemented in the ports
tree, if you install it from ports you will have identical result to
downloading from wordpress.org and extract it manually.

The difference as stated above, is that the FreeBSD port includes the
files for *development* of Joomla, the official download has all the
files necessay to build a website based on Joomla.

It may be that there are people using FreeBSD to develop Joomla, then of
course this port are for them, although a more proper naming would be
joomla3-devel or somesuch.


joomla-devel would kind of imply that you're installing the "devel" version
of it, not that it includes the devel LIBS.  This seems to be a standard
wording for ports (see locate /usr/ports/ | grep \\\-devel | grep pkg-descr
| xargs cat )

What makes more sense to me is that the Dev files would be part of a
non-default option -- whether that's included with the normal .tar.gz or
requires the github copy, I can't say.

I don't know if there's a *canonical* naming that universally means this is
what '-devel' means.


Errr, ICBW (one needs to look at the history of the port), but in
FreeBSD a -devel version of the port is usually created when somebody
wants to be able to install a version that is currently under
development and yet keep the ability for normal users to use the stable
version.  In these cases, a second port is created (once upon a time
this was done by a repository copy to preserve the port's history) that
is exactly the same as the first one, and then the port maintainer
updates the second port (the -devel one) to a newer version.


I feel like we're in agreement here.  You install -devel if you want the 
"experimental" or "beta" version of a port.  It's not necessarily an 
install of a "Dev kit".  (Compare this with debian, where the -dev suffix 
on a package includes the .h files required to build a thing from 
scratch).


My questions were meta to the discussion about how to fix Joomla:

My question was "is this by tradition or is there a formal point here 
(say, in the porter's handbook) that this is the only thing -devel should 
be used for?"


If not, are there exceptions, a case where -devel means something 
different?  And if that's the case, should a different name be chosen?


Are there any suffixes like this, which aren't necessarily flavorable, 
since the -devel version of a port may be significantly different from the 
release version.  So, not like -nox11, or is -devel unique this way?


Also, should -devel by default include -debug -- after all, if you're 
installing the beta of a software, it might be assumed you have interest 
in reporting issues?


-Dan

--


Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
FB:  fb.com/DanielMahoneyIV
LI:   linkedin.com/in/gushi
Site:  http://www.gushi.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: Phabricator to ports commit broken?

2018-05-21 Thread Kurt Jaeger 
Hi!

> I'm getting some issues due to these systems: svn hooks and phabricator 
> apparently being out of sync:
> 
> Can anyone help or suggest a way forward?

Eitan Adler wrote on phabric-admin@:

> Not currently. https://secure.phabricator.com/T2920 is the upstream
> tracking bug.

-- 
p...@opsec.eu+49 171 31013722 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"

Re: www/joomla3 port installs from GitHub, why?

2018-05-21 Thread Peter Pentchev 
On Sun, May 20, 2018 at 04:49:34PM -0700, Dan Mahoney (Gushi) wrote:
> On Sun, 20 May 2018, Per olof Ljungmark wrote:
> 
> > On 05/20/18 21:15, Eugene Grosbein wrote:
> > > 21.05.2018 2:02, Per olof Ljungmark wrote:
> 
> > OK, I'll try to explain a bit more.
> > 
> > Firstly, this port is PHP code and needs no compilation, so they are
> > both source files. NO_BUILD=   yes
> > 
> > www/wordpress is a similar port, correctly implemented in the ports
> > tree, if you install it from ports you will have identical result to
> > downloading from wordpress.org and extract it manually.
> > 
> > The difference as stated above, is that the FreeBSD port includes the
> > files for *development* of Joomla, the official download has all the
> > files necessay to build a website based on Joomla.
> > 
> > It may be that there are people using FreeBSD to develop Joomla, then of
> > course this port are for them, although a more proper naming would be
> > joomla3-devel or somesuch.
> 
> joomla-devel would kind of imply that you're installing the "devel" version
> of it, not that it includes the devel LIBS.  This seems to be a standard
> wording for ports (see locate /usr/ports/ | grep \\\-devel | grep pkg-descr
> | xargs cat )
> 
> What makes more sense to me is that the Dev files would be part of a
> non-default option -- whether that's included with the normal .tar.gz or
> requires the github copy, I can't say.
> 
> I don't know if there's a *canonical* naming that universally means this is
> what '-devel' means.

Errr, ICBW (one needs to look at the history of the port), but in
FreeBSD a -devel version of the port is usually created when somebody
wants to be able to install a version that is currently under
development and yet keep the ability for normal users to use the stable
version.  In these cases, a second port is created (once upon a time
this was done by a repository copy to preserve the port's history) that
is exactly the same as the first one, and then the port maintainer
updates the second port (the -devel one) to a newer version.

G'luck,
Peter

-- 
Peter Pentchev  roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

FreeBSD ports you maintain which are out of date

2018-05-21 Thread 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
+-+
audio/qsynth| 0_5_0   | qsynth_0_5_1
+-+


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: www/joomla3 port installs from GitHub, why?

2018-05-21 Thread Per olof Ljungmark 
On 05/21/18 01:49, Dan Mahoney (Gushi) wrote:
> On Sun, 20 May 2018, Per olof Ljungmark wrote:
> 
>> On 05/20/18 21:15, Eugene Grosbein wrote:
>>> 21.05.2018 2:02, Per olof Ljungmark wrote:
> 
>> OK, I'll try to explain a bit more.
>>
>> Firstly, this port is PHP code and needs no compilation, so they are
>> both source files. NO_BUILD=   yes
>>
>> www/wordpress is a similar port, correctly implemented in the ports
>> tree, if you install it from ports you will have identical result to
>> downloading from wordpress.org and extract it manually.
>>
>> The difference as stated above, is that the FreeBSD port includes the
>> files for *development* of Joomla, the official download has all the
>> files necessay to build a website based on Joomla.
>>
>> It may be that there are people using FreeBSD to develop Joomla, then of
>> course this port are for them, although a more proper naming would be
>> joomla3-devel or somesuch.
> 
> joomla-devel would kind of imply that you're installing the "devel"
> version of it, not that it includes the devel LIBS.  This seems to be a
> standard wording for ports (see locate /usr/ports/ | grep \\\-devel |
> grep pkg-descr | xargs cat )
> 
> What makes more sense to me is that the Dev files would be part of a
> non-default option -- whether that's included with the normal .tar.gz or
> requires the github copy, I can't say.

That sounds as a good solution - both are available at Github - will try
to suggest a patch.

___
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"