Using INSTALL_DATA to install header files to PREFIX/include/PORTNAME

[Marcel Bonnet]

Hello, porters!

I've been reading the Porters Handbook, even the bsd.*.mk files... but
I'm wondering: why the waf installer put all the installation files
into STAGEDIR but the port system do not copy them all, just some of
them to the PREFIX.

Below the Makefile and pkg-plist.

If do not type
${INSTALL_DATA} ${STAGEDIR}${PREFIX}/include/sord-0/sord/sord.h
${STAGEDIR}${PREFIX}/include/sord-0/sord/
them the this header is not copied to PREFIX. But the other files are
installed normally .

So, I don't understand why I have to say ${INSTALL_DATA} the file from
and to its current directory. Am I'm doing something really wrong, but
perhaps produced the desired effect? Now its working like a charm.


The Makefile :

do-install:
(cd ${WRKSRC}/build && ${INSTALL_DATA} sord-0.pc \
   ${STAGEDIR}${PREFIX}/libdata/pkgconfig)
${REINPLACE_CMD} "s,^prefix=.*,prefix=${PREFIX},"
${STAGEDIR}${PREFIX}/libdata/pkgconfig/sord-0.pc
${RM} ${STAGEDIR}${PREFIX}/libdata/pkgconfig/sord-0.pc.bak
(cd ${WRKSRC} && ${WAF_CMD} install)
${INSTALL_DATA} ${STAGEDIR}${PREFIX}/include/sord-0/sord/sord.h
${STAGEDIR}${PREFIX}/include/sord-0/sord/
${INSTALL_DATA} ${STAGEDIR}${PREFIX}/include/sord-0/sord/sordmm.hpp
${STAGEDIR}${PREFIX}/include/sord-0/sord/
${STRIP_CMD} ${STAGEDIR}${PREFIX}/bin/sordi
${STRIP_CMD} ${STAGEDIR}${PREFIX}/bin/sord_validate
${STRIP_CMD} ${STAGEDIR}${PREFIX}/lib/libsord-0.so.0.12.2


$ cat pkg-plist
bin/sordi
bin/sord_validate
include/sord-0/sord/sord.h
include/sord-0/sord/sordmm.hpp
lib/libsord-0.so
lib/libsord-0.so.0
lib/libsord-0.so.0.12.2
libdata/pkgconfig/sord-0.pc
man/man1/sordi.1.gz
man/man1/sord_validate.1.gz


The complete files are here:
https://github.com/marcelbonnet/freebsd-ports/tree/ardour5.3/textproc/sord-0

Thanks,

-- 
Marcel Bonnet
github.com/marcelbonnet/
___
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: openntpd-5.7p4_2,2 depends on libressl-2.2.6 ?!

[Christian Weisgerber]

Joe Holden:

> I should be able to use rdomains in software ported from OpenBSD yes?

You should, yes.  Rtables are equivalent to FIBs, see setfib(1/2),
and the net/openntpd port supports "rtable" on FreeBSD.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de
___
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/subsonic-standalone license

[Joshua Ruehlig]

Ahh ok, sounds good.

Sounds like we should just follow suit with whatever www/subsonic does.
Which seems to be thus far to remove the LICENSE line.

On Fri, Oct 28, 2016 at 9:38 AM, Franco Fichtner 
wrote:

>
> > On 28 Oct 2016, at 6:30 PM, Joshua Ruehlig 
> wrote:
> >
> > I don't believe the maintainer dropped the project.
>
> I was talking about www/subsonic, sorry for the confusion:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213298
>
> > If a user wants to use a previous version they are free to modify the
> PORTVERSION, update the 'distinfo', and build the port. Also the
> 'www/subsonic' port is still on version 5.3 so people can use that as well.
>
> That's impractical for users who use packages.  :)
>
>
> Cheers,
> Franco
___
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/subsonic-standalone license

[Vlad K.]

On 2016-10-28 18:38, Franco Fichtner wrote:


I was talking about www/subsonic, sorry for the confusion:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213298



This bug shows the discussion I had with the Subsonic maintainer (who 
is, technically, until that patch is committed, still a maintainer) and 
carries the whole context. In short, the author of Subsonic has to 
specify what is the license of his product and include appropriate 
license in both the distributable/downloadable tarball and relevant 
source repositories.


As it is at the moment, it all points to it still being GPL'd, despite 
his announcements on the forum post linked in the issue, because the 
downloadable tarballs, at the time, I checked, still carried a README 
saying it's GPL'd.


A forum post is inadequate license change and the author should know 
better. His tarballs must include appropriate license whichever it is.


IMHO, the FreeBSD ports tree cannot continue to carry that port, 6.0+ 
onward because afaik one cannot retroactively change the licene of 
previous releases, until the license is well known and port possibly 
RESTRICTED if the license requires it. For example see Oracle JRE ports 
that require you to manually download the distfiles and agree to 
Oracle's license apriori.




--

Vlad K.
___
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/subsonic-standalone license

[Franco Fichtner]

> On 28 Oct 2016, at 6:30 PM, Joshua Ruehlig  wrote:
> 
> I don't believe the maintainer dropped the project.

I was talking about www/subsonic, sorry for the confusion:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213298

> If a user wants to use a previous version they are free to modify the 
> PORTVERSION, update the 'distinfo', and build the port. Also the 
> 'www/subsonic' port is still on version 5.3 so people can use that as well.

That's impractical for users who use packages.  :)


Cheers,
Franco
___
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"

Secret Shopper

[ashley brown]

Hello my name is ashley and im interested in the job. My phone number is
727-318-9147.
___
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/subsonic-standalone license

[Joshua Ruehlig]

Did you read the post Michael linked? Version 6.0 is no longer GPLv3
because he added some code that couldn't be added to a GPL project. I don't
believe the maintainer dropped the project.
If a user wants to use a previous version they are free to modify the
PORTVERSION, update the 'distinfo', and build the port. Also the
'www/subsonic' port is still on version 5.3 so people can use that as well.

I could not find a license for version 6.0. I checked the README.TXT that
came with the v6.0 jar and it does not seem to be up to date. It says
subsonic is "free software" and under the GPL.
I think we should remove the LICENSE line from the Makefile, not sure what
else we should do.

Thanks,
Josh

On Fri, Oct 28, 2016 at 9:09 AM, Franco Fichtner 
wrote:

>
> > On 28 Oct 2016, at 5:53 PM, Joshua Ruehlig 
> wrote:
> >
> > Franco, what do you mean a maintainer drop?
> > Also Madsonic, which is supposedly GPL based on their website is
> available.
>
> The maintainer resigned, but updated to 6.0 because there were no
> distfiles,
> and the code seemed to be gone for 5.3 is now on GitHub:
>
> https://github.com/sindremehus/subsonic
>
> I don't know whether 6.0 is quintessential, but from a pure license
> perspective
> it seems odd that everyone now has to use a proprietary license with no
> options
> given even though we still have the original 5.3 *and* a fork which could
> very
> well gain traction of a port was added as an alternative.
>
> Just for the record, I know this takes work.  Not asking for it to be done,
> simply wondering why this happened the way it did.
>
>
> Cheers,
> Franco
___
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/subsonic-standalone license

[Franco Fichtner]

> On 28 Oct 2016, at 5:53 PM, Joshua Ruehlig  wrote:
> 
> Franco, what do you mean a maintainer drop?
> Also Madsonic, which is supposedly GPL based on their website is available.

The maintainer resigned, but updated to 6.0 because there were no distfiles,
and the code seemed to be gone for 5.3 is now on GitHub:

https://github.com/sindremehus/subsonic

I don't know whether 6.0 is quintessential, but from a pure license perspective
it seems odd that everyone now has to use a proprietary license with no options
given even though we still have the original 5.3 *and* a fork which could very
well gain traction of a port was added as an alternative.

Just for the record, I know this takes work.  Not asking for it to be done,
simply wondering why this happened the way it did.


Cheers,
Franco
___
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: Thread issues

[Matthew Seaman]

On 2016/10/28 16:45, The Doctor wrote:
> I tought FreeBSD is POSIX threads compliant.

It is, but unlike linux you need to use -lpthread on the compilation
command line to use all of the threading functionality.  So the question
is: why didn't configure succeed in its test for exactly that?

> checking for the pthreads library -lpthreads... no
> checking whether pthreads work without any flags... no
> checking whether pthreads work with -Kthread... no
> checking whether pthreads work with -kthread... no
> checking for the pthreads library -llthread... no
> checking whether pthreads work with -pthread... no
> checking whether pthreads work with -pthreads... no
> checking whether pthreads work with -mt... no
> checking whether pthreads work with -mthreads... no
> checking for the pthreads library -lpthread... no<<<
> checking whether pthreads work with --thread-safe... no
> checking for pthread-config... no

Cheers,

Matthew




signature.asc
Description: OpenPGP digital signature

Re: www/subsonic-standalone license

[Joshua Ruehlig]

Ohh, I realize earlier I'm not the maintainer and was only CC'ed on the
first email. Regardless I'll go search to see if I can find the license for
subsonic 6.0.

Franco, what do you mean a maintainer drop?
Also Madsonic, which is supposedly GPL based on their website is available.

Thanks,
Josh

On Fri, Oct 28, 2016 at 7:57 AM, Franco Fichtner 
wrote:

>
> > On 28 Oct 2016, at 4:41 PM, Joshua Ruehlig 
> wrote:
> >
> > sure I'll take a look. I assume all I need to do is find and set the
> > current license?
>
> I would like to take this opportunity to ask why we have a maintainer
> drop whilst doing the upgrade of a free 5.3 to a proprietary 6.0.
>
> What's the logic in that?  Wouldn't it be better to have keep 5.3 until
> it dies in dignity?
>
> Also, there is https://github.com/Libresonic/libresonic
>
>
> Cheers,
> Franco
>
___
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"

Thread issues

[The Doctor]

Script started on Fri Oct 28 09:40:37 2016
You have mail.
root@doctor:/usr/home/doctor # portmascd 
/usr/source/php-7.0.13RC!

/usr/source/php-7.0.13RC!: No such file or directory.
root@doctor:/usr/home/doctor # cd /usr/source/php-7.0.13RC!1

root@doctor:/usr/source/php-7.0.13RC1 # portmaster math/fftw3-float ; 
portmaster  math/fftw3 ; /bin/sh ./configphp ; less configphp

]0;portmaster: fftw3-float-3.3.3_2
===>>> Currently installed version: fftw3-float-3.3.3_2
===>>> Port directory: /usr/ports/math/fftw3-float

===>>> Gathering distinfo list for installed ports

===>>> Launching 'make checksum' for math/fftw3-float in background
===>>> Gathering dependency list for math/fftw3-float from ports
===>>> Initial dependency check complete for math/fftw3-float

]0;portmaster: fftw3-float-3.3.3_2
===>>> Starting build for math/fftw3-float <<<===

===>>> All dependencies are up to date

===>  Cleaning for fftw3-float-3.3.5
===>  License GPLv2 accepted by the user
===>  Found saved configuration for fftw3-float-3.3.5
===>   fftw3-float-3.3.5 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by fftw3-float-3.3.5 for building
===>  Extracting for fftw3-float-3.3.5
=> SHA256 Checksum OK for fftw-3.3.5.tar.gz.
===>  Patching for fftw3-float-3.3.5
===>  Applying extra patch 
/usr/ports/math/fftw3-float/../../math/fftw3/files/extrapatch-tests_fftw-bench.c
===>  Applying FreeBSD patches for fftw3-float-3.3.5
===>   fftw3-float-3.3.5 depends on package: pkgconf>=0.9.10 - found
===>   fftw3-float-3.3.5 depends on executable: gcc48 - found
===>   fftw3-float-3.3.5 depends on file: /usr/local/bin/as - found
===>   fftw3-float-3.3.5 depends on package: perl5>=5.24<5.25 - found
===>   fftw3-float-3.3.5 depends on shared library: libmpi.so - found 
(/usr/local/mpi/openmpi/lib/libmpi.so)
===>  Configuring for fftw3-float-3.3.5
configure: loading site script /usr/ports/Templates/config.site
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p
checking for gawk... (cached) /usr/bin/awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... amd64-portbld-freebsd11.0
checking host system type... amd64-portbld-freebsd11.0
checking for gcc... gcc48
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc48 accepts -g... yes
checking for gcc48 option to accept ISO C89... none needed
checking whether gcc48 understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc48... gcc3
checking for C compiler vendor... gnu
checking for gcc48 option to accept ISO C99... -std=gnu99
checking for gcc48 -std=gnu99 option to accept ISO Standard C... (cached) 
-std=gnu99
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking how to print strings... printf
checking for a sed that does not truncate output... (cached) /usr/bin/sed
checking for grep that handles long lines and -e... (cached) /usr/bin/grep
checking for egrep... (cached) /usr/bin/egrep
checking for fgrep... (cached) /usr/bin/fgrep
checking for ld used by gcc48 -std=gnu99... /usr/local/bin/ld
checking if the linker (/usr/local/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/local/bin/nm
checking the name lister (/usr/local/bin/nm) interface... BSD nm
checking the maximum length of command line arguments... (cached) 262144
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... no
checking how to convert amd64-portbld-freebsd11.0 file names to 
amd64-portbld-freebsd11.0 format... func_convert_file_noop
checking how to convert amd64-portbld-freebsd11.0 file names to toolchain 
format... func_convert_file_noop
checking for /usr/local/bin/ld option to reload object files... -r
checking for objdump... /usr/local/bin/objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... dlltool
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... /usr/local/bin/ranlib
checking command to parse /usr/local/bin/nm output from gcc48 -std=gnu99 
object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... cpp48
checking for ANSI C header files... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... 

Re: www/subsonic-standalone license

[Franco Fichtner]

> On 28 Oct 2016, at 4:41 PM, Joshua Ruehlig  wrote:
> 
> sure I'll take a look. I assume all I need to do is find and set the
> current license?

I would like to take this opportunity to ask why we have a maintainer
drop whilst doing the upgrade of a free 5.3 to a proprietary 6.0.

What's the logic in that?  Wouldn't it be better to have keep 5.3 until
it dies in dignity?

Also, there is https://github.com/Libresonic/libresonic


Cheers,
Franco
___
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/subsonic-standalone license

[Joshua Ruehlig]

sure I'll take a look. I assume all I need to do is find and set the
current license?

On Oct 28, 2016 6:41 AM, "Michael Zhilin"  wrote:

> Hi,
>
> Issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213299 (created
> 20 days ago).
>
> License of www/subsonic-standalone is GPL [1], but actually this version
> of software (v.6) is available only as free binaries. Also it includes
> trial version of functionalities which can be purchased by subscription.
>
> Could you please look at this issue?
>
> Thank you in advance!
>
___
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: Problem with gcc5 std library when building ports

[Patrick Powell]

On 10/26/16 16:01, Dewayne Geraghty wrote:

Have spent a couple of days trying to build around 800 ports with gcc5.
This one has me stumped!

Can anyone help regarding the apparant absence of snprintf from std?  Am I
missing something, perhaps LDCONFIG or?  I've looked in /usr/ports/Mk/
bsd.gcc.mk and /usr/ports/Mk/bsd.port.mk but this is an area that I'm
unfamiliar, so nothing really stood out.

If I change the compiler from gcc5 to clang everything compiles and runs
correctly. I have in /etc/make.conf
USE_GCC=  5
and to use clang, I just comment out the above. So everything is constant,
on FreeBSD 10.3Stable (updated and rebuilt overnight)

For example: /usr/ports/devel/jsoncpp (but many share this problem)
g++5 -o buildscons/linux-gcc-FreeBSD/src/lib_json/json_reader.o -c -O2
-pipe -DOPENSSL_NO_SSL2 -DOPENSSL_NO_SSL3 -g0 -ggdb0 -DSTRIP_FBSDID
-UDEBUGGING -UDEBUG -march=c3-2 -mtune=c3-2 -Wl,-rpath=/usr/local/lib/gcc5
-fno-strict-aliasing --std=c++11 -Wl,-rpath=/usr/local/lib/gcc5 -Iinclude
src/lib_json/json_reader.cpp

src/lib_json/json_reader.cpp: In member function 'std::__cxx11::string
Json::Reader::getLocationLineAndColumn(Json::Reader::Location) const':
src/lib_json/json_reader.cpp:34:18: error: 'snprintf' is not a member of
'std'
  #define snprintf std::snprintf

And for completeness:
# ldconfig -r | grep -E "gcc|\+"
 search directories:
/lib:/usr/lib:/usr/lib/compat:/usr/local/lib:/usr/local/lib/gcc5:/usr/local/lib/heimdal:/usr/local/lib/perl5/5.20/mach/CORE
 35:-lgcc_s.1 => /lib/libgcc_s.so.1
 38:-lc++.1 => /usr/lib/libc++.so.1
 126:-lcc1.0 => /usr/local/lib/gcc5/libcc1.so.0
 127:-lgcc_s.1 => /usr/local/lib/gcc5/libgcc_s.so.1
 128:-lstdc++.6 => /usr/local/lib/gcc5/libstdc++.so.6
 129:-lcilkrts.5 => /usr/local/lib/gcc5/libcilkrts.so.5
 130:-lssp.0 => /usr/local/lib/gcc5/libssp.so.0
 131:-lquadmath.0 => /usr/local/lib/gcc5/libquadmath.so.0
 132:-lgfortran.3 => /usr/local/lib/gcc5/libgfortran.so.3
 133:-lobjc.4 => /usr/local/lib/gcc5/libobjc.so.4
 134:-lgomp.1 => /usr/local/lib/gcc5/libgomp.so.1
 135:-lgomp-plugin-host_nonshm.1 =>
/usr/local/lib/gcc5/libgomp-plugin-host_nonshm.so.1
 136:-litm.1 => /usr/local/lib/gcc5/libitm.so.1
 137:-latomic.1 => /usr/local/lib/gcc5/libatomic.so.1

Regards, Dewayne
___
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"



Way way back in the early days of the standardization of the C library,  
the Great Minds decided that putting snprintf into the C library would 
not be done as it was 'not part of the deployed routines' or something 
similar.  So they left in sprintf,  which ended up causing more boundary 
overruns and attacks then any other routine.  Don't get me started about 
strcpy, etc. etc.


--
Patrick Powell Astart Technologies
papow...@astart.com1530 Jamacha Rd, Suite X
Network and System San Diego, CA 92019
  Consulting   858-874-6543 FAX 858-751-2435
Web: www.astart.com

___
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: New FreeBSD port

[Kurt Jaeger]

Hello,

> Hello FreeBSD Ports Management Team,
> 
> recently i have ported a Linux application to FreeBSD for my personal
> needs. I think it could be of benefit of other FreeBSD users to have the
> application under the ports tree.
> 
> What is the usual procedure to create a new FreeBSD port ?

It's described in full in the Porters Handbook at

https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html

There's a short intro called "Quick Porting" in section 3 of that handbook:

https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#quick-porting

I'd suggest you have a look at that section, give it a first cut
and ask additional questions in the list. 

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

www/subsonic-standalone license

[Michael Zhilin]

Hi,

Issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213299 (created 20
days ago).

License of www/subsonic-standalone is GPL [1], but actually this version of
software (v.6) is available only as free binaries. Also it includes trial
version of functionalities which can be purchased by subscription.

Could you please look at this issue?

Thank you in advance!
___
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: Inconsistency? (was Re: misc/jive deleted)

[Patrick Powell]

On 10/26/16 03:56, David Demelier wrote:

On 10/26/2016 09:32 AM, Kurt Jaeger wrote:

Hi!


I think unless FreeBSD makes explicit antichrist statement, there is
no problem having a daemon mascot. I have never heard any religious
problem so far. Or then I missed something.

Approx. 20 years ago (?), some FreeBSD developer with a old-style
logo on a t-shirt was asked to leave some saloon in Texas
because the logo suggested that they worship the antichrist.

Brilliant ! :-)

There was a job (in rec.humor.funny?) about it 8-}

That's why this reference to the demon logo is made 8-}



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



I have an autographed T Shirt by the artist -  Phil Foglio.  Who also 
did the artwork for the MythAdventures (Graphic Novel) as well as 
others.  When asked for an update at one of the San Diego Comic Cons,  
he just laughed hysterically and then politely said 'No!'


See http://www.studiofoglio.com/ for examples of his work.

--
Patrick Powell Astart Technologies
papow...@astart.com1530 Jamacha Rd, Suite X
Network and System San Diego, CA 92019
  Consulting   858-874-6543 FAX 858-751-2435
Web: www.astart.com

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

New FreeBSD port

[vladimirtt]

Hello FreeBSD Ports Management Team,

recently i have ported a Linux application to FreeBSD for my personal
needs. I think it could be of benefit of other FreeBSD users to have the
application under the ports tree.

What is the usual procedure to create a new FreeBSD port ?


Best regards,

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

Update to nzbget port

[Nicolas]

Hi

I have successfully updated the nzbget port to 0.17.1 and ran it without 
issues on FreeBSD 10.3 amd64.


To compile it with clang 3.4, I have added the following things 
"-std=c++1y -stdlib=libc++" to the Makefile on the CPPFLAGS line.


To create the package, I have removed the AUTHORS entry in pkg-plist

I don't know if this is the best way to update the port.

The diff is attached to this email

If this is the correct way, I will submit it to bugzilla

Regards

Nicolas

Index: Makefile
===
--- Makefile(revision 424760)
+++ Makefile(working copy)
@@ -2,8 +2,8 @@
 # $FreeBSD$

 PORTNAME=  nzbget
-PORTVERSION=   16.4
-PORTREVISION=  3
+PORTVERSION=   17.1
+PORTREVISION=  1
 DISTVERSIONPREFIX= v
 CATEGORIES=news

@@ -21,7 +21,7 @@
--with-libcurses-libraries=${NCURSESLIB}
 CONFIGURE_ENV= LOCALBASE="${LOCALBASE}"
 MAKE_JOBS_UNSAFE=  yes
-CPPFLAGS+= -I${LOCALBASE}/include
+CPPFLAGS+= -I${LOCALBASE}/include -std=c++1y -stdlib=libc++
 LDFLAGS+=  -lpthread
 BINMODE=   0755

Index: distinfo
===
--- distinfo(revision 424760)
+++ distinfo(working copy)
@@ -1,2 +1,2 @@
-SHA256 (nzbget-nzbget-v16.4_GH0.tar.gz) = 07229ee57a1dd16d154c949708f6632e92b92a9fb8a651867c915da81ca81af6
-SIZE (nzbget-nzbget-v16.4_GH0.tar.gz) = 1591305
+SHA256 (nzbget-nzbget-v17.1_GH0.tar.gz) = 4b3cf500d9bb6e9ab65b2c8451358e6c93af0368176f193eebafca17d7209c39
+SIZE (nzbget-17.1-src.tar.gz) = 1609931
Index: pkg-plist
===
--- pkg-plist   (revision 424760)
+++ pkg-plist   (working copy)
@@ -1,7 +1,6 @@
 bin/nzbget
 @sample etc/nzbget.conf.sample
 @comment %%PORTDOCSDOCSDIR%%/COPYING
-%%PORTDOCSDOCSDIR%%/AUTHORS
 %%PORTDOCSDOCSDIR%%/ChangeLog
 %%PORTDOCSDOCSDIR%%/README
 %%DATADIR%%/nzbget.conf
___
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: lighttpd 1.4.42 update does not work with FreeBSD 9.3

[Guido Falsi]

On 10/28/16 11:11, Cedric Berger wrote:
> Since the update 6 days ago, lighttpd 1.4.42 does not work on FreeBSD 9.3 
> anymore.
> 
> The binary fails to startup with:
> 
> 2016-10-28 11:06:30: (plugin.c.227) dlopen() failed for: 
> /usr/local/lib/lighttpd/mod_cgi.so /usr/local/lib/lighttpd/mod_cgi.so: 
> Undefined symbol "pipe2” 
> 
> mod_cgi.c contains the following horror:
> 
> #ifdef O_CLOEXEC
> #define pipe_cloexec(pipefd) pipe2((pipefd), O_CLOEXEC)
> #elif defined FD_CLOEXEC
> #define pipe_cloexec(pipefd) \
>   (   0 == pipe(pipefd) \
>&& 0 == fcntl(pipefd[0], F_SETFD, FD_CLOEXEC) \
>&& 0 == fcntl(pipefd[1], F_SETFD, FD_CLOEXEC) \
> ? 0 \
> : -1)
> #else
> #define pipe_cloexec(pipefd) pipe(pipefd)
> #endif
> 
> Which of course is wrong, FreeBSD 9.3 has O_CLOEXEC but no pipe2.
> 

Please file a bug report about this.

-- 
Guido Falsi 
___
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: lighttpd does not pull OpenSSL dependency

[Guido Falsi]

On 10/28/16 11:28, David Demelier wrote:
> 2016-10-27 18:35 GMT+02:00 Mathieu Arnold :
>> Le 27/10/2016 à 17:00, Matthew D. Fuller a écrit :
>>> On Thu, Oct 27, 2016 at 03:05:03PM +0200 I heard the voice of
>>> Mathieu Arnold, and lo! it spake thus:
 Once you install openssl from ports, the ports framework will use
 it, always.
>>> That is absolutely not the case since OpenSSL in base was updated to
>>> .so.8 and ports wasn't re-bumped past it.  Everything gets confused
>>> all the time.
>>
>> Well, that is another problem, and you are right, OpenSSL's shlib should
>> have been bumped, blame the former maintainer for that. I'll talk to the
>> new maintainer about that.
> 
> What if we rename contrib libs that are used only in base?
> 
> like:
> 
> - /usr/lib/libfreebsd-(ssl|crypto)
> - /usr/lib/libfreebsd-kerberos* (don't know the name, I don't have
> access to a FreeBSD system ATM)
> 
> And then, ports must always link to OpenSSL from ports or Kerberos,
> and so on that is in base but only for base tools.

That's what "making the library private" in base means.

Base already has some libraries in it which are "private", that means
not exposed to binaries outside of base for compiling or linking against.

-- 
Guido Falsi 
___
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: lighttpd does not pull OpenSSL dependency

[David Demelier]

2016-10-27 18:35 GMT+02:00 Mathieu Arnold :
> Le 27/10/2016 à 17:00, Matthew D. Fuller a écrit :
>> On Thu, Oct 27, 2016 at 03:05:03PM +0200 I heard the voice of
>> Mathieu Arnold, and lo! it spake thus:
>>> Once you install openssl from ports, the ports framework will use
>>> it, always.
>> That is absolutely not the case since OpenSSL in base was updated to
>> .so.8 and ports wasn't re-bumped past it.  Everything gets confused
>> all the time.
>
> Well, that is another problem, and you are right, OpenSSL's shlib should
> have been bumped, blame the former maintainer for that. I'll talk to the
> new maintainer about that.

What if we rename contrib libs that are used only in base?

like:

- /usr/lib/libfreebsd-(ssl|crypto)
- /usr/lib/libfreebsd-kerberos* (don't know the name, I don't have
access to a FreeBSD system ATM)

And then, ports must always link to OpenSSL from ports or Kerberos,
and so on that is in base but only for base tools.

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

lighttpd 1.4.42 update does not work with FreeBSD 9.3

[Cedric Berger]

Since the update 6 days ago, lighttpd 1.4.42 does not work on FreeBSD 9.3 
anymore.

The binary fails to startup with:

2016-10-28 11:06:30: (plugin.c.227) dlopen() failed for: 
/usr/local/lib/lighttpd/mod_cgi.so /usr/local/lib/lighttpd/mod_cgi.so: 
Undefined symbol "pipe2” 

mod_cgi.c contains the following horror:

#ifdef O_CLOEXEC
#define pipe_cloexec(pipefd) pipe2((pipefd), O_CLOEXEC)
#elif defined FD_CLOEXEC
#define pipe_cloexec(pipefd) \
  (   0 == pipe(pipefd) \
   && 0 == fcntl(pipefd[0], F_SETFD, FD_CLOEXEC) \
   && 0 == fcntl(pipefd[1], F_SETFD, FD_CLOEXEC) \
? 0 \
: -1)
#else
#define pipe_cloexec(pipefd) pipe(pipefd)
#endif

Which of course is wrong, FreeBSD 9.3 has O_CLOEXEC but no pipe2.

Thanks,
Cedric

___
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 you maintain which are out of date

[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
+-+
net/p5-Net-Ping | 2.41| 2.55
+-+
science/metaf2xml   | 2.0 | 2.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"