How to get -RC2 is tarball name?

[Gary Aitken]

I'm trying to fetch:
  https://download.gimp.org/mirror/pub/gimp/v2.10/gimp-2.10.0-RC2.tar.bz2
Both the RC2 and the bz2 are giving me problems.
I've tried every combination I can think of and can't seem to get the
right thing.  In order to get the -RC2 I had to resort to:

PORTNAME?=  gimp-devel-app
DISTVERSION=2.10.0
GIMPVERSION=RC2
DISTNAME=gimp-${DISTVERSION}-${GIMPVERSION}
MASTER_SITES=   https://download.gimp.org/mirror/pub/gimp/v2.10/

but that asks for .../v2.10/gimp-2.10.0-RC2.tar.gz
tacking the .tar.bz2 on the end of DISTNAME doesn't help.

I know this totally ignores all the other directives about
  MASTER_SITES= GIMP
and recommendations for PORT/DIST NAME and VERSION, but I can't get
any other combination to get even this far.

Is there a way to get the portname "gimp-devel-app" truncated to "gimp"
with some operator X in ${PORTNAME:X}?  I didn't see them described in
the handbook.

Is there a variable I can override for the tar.bz2 part?

Thanks,
Gary
___
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: request for a new port + package

[Eugene Grosbein]

20.04.2018 3:22, Julian Elischer wrote:

>> The package is created automatically once new port is created and added
>> to FreeBSD Ports collection. You can create and submit new port yourself,
>> just read https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
> 
> It seems to me that the description of what to do to make a port
> is somewhat recursive by which I mean you need to understand
> what it says before you read it. if you don't already know the jargon,
> it is all Greek. (Apologies to any Greeks on the list).

That means the language should be simplified (or thesaurus added :-)

> I think it would be a pretty cool project to write a tool that asks
> lots of questions and then eventually spits out a port Makefile.

I don't believe this is possible for ports other that are trivial to create 
without any tool.

> it could allow the user to browse to places and then analyse the
> links used etc.
> I think the port writer's handbook is a bit intimidating to new ports 
> submitters.

___
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: request for a new port + package

[Julian Elischer]

On 9/4/18 7:15 pm, Eugene Grosbein wrote:

On 09.04.2018 14:16, Mayuresh Kathe wrote:


how do i place a request for a new port + package?
the sources for my requested tool are available at
http://www.t3x.org/files/zenlisp.zip and the author of that tool has
granted permission to move it from the existing "public domain" license
to any "bsdl" license.

The package is created automatically once new port is created and added
to FreeBSD Ports collection. You can create and submit new port yourself,
just read https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/


It seems to me that the description of what to do to make a port
is somewhat recursive by which I mean you need to understand
what it says before you read it. if you don't already know the jargon,
it is all Greek. (Apologies to any Greeks on the list).
I think it would be a pretty cool project to write a tool that asks
lots of questions and then eventually spits out a port Makefile.
it could allow the user to browse to places and then analyse the
links used etc.
I think the port writer's handbook is a bit intimidating to new ports 
submitters.






___
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: cannot compile www/node

[Matthew D. Fuller]

On Thu, Apr 19, 2018 at 07:06:32PM +0200 I heard the voice of
Wojciech Puchar, and lo! it spake thus:
>
> /usr/bin/ld:/usr/ports/www/node/work/node-v9.11.1/out/Release/obj.target/deps/v8/src/libv8_base.a:
>  
> file format not recognized; treating as linker script

I've gotten this (well, something that looks like this anyway; I don't
have a recent error handy so I'm going by memory) regularly on node
for 6 months or so.  My workaround is to set CXX to a clang I've got
around from ports, and then it gets through fine.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
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"

cannot compile www/node

[Wojciech Puchar]

  c++ -pthread -rdynamic -m64 -Wl,--export-dynamic   -fstack-protector -o 
/usr/ports/www/node/work/node-v9.11.1/out/Release/mksnapshot 
-Wl,--start-group 
/usr/ports/www/node/work/node-v9.11.1/out/Release/obj.target/mksnapshot/deps/v8/src/snapshot/mksnapshot.o 
/usr/ports/www/node/work/node-v9.11.1/out/Release/obj.target/deps/v8/src/libv8_base.a 
/usr/ports/www/node/work/node-v9.11.1/out/Release/obj.target/deps/v8/src/libv8_builtins_setup.a 
/usr/ports/www/node/work/node-v9.11.1/out/Release/obj.target/deps/v8/src/libv8_libbase.a 
/usr/ports/www/node/work/node-v9.11.1/out/Release/obj.target/deps/v8/src/libv8_libplatform.a 
/usr/ports/www/node/work/node-v9.11.1/out/Release/obj.target/deps/v8/src/libv8_nosnapshot.a 
/usr/ports/www/node/work/node-v9.11.1/out/Release/obj.target/deps/v8/src/libv8_libsampler.a 
/usr/ports/www/node/work/node-v9.11.1/out/Release/obj.target/deps/v8/src/libv8_builtins_generators.a 
-lz -L/usr/local/lib -luv -lcares -lcrypto -lssl -licui18n -licuuc 
-licudata -lelf -L/usr/local/lib -lexecinfo -Wl,--end-group
/usr/bin/ld:/usr/ports/www/node/work/node-v9.11.1/out/Release/obj.target/deps/v8/src/libv8_base.a: 
file format not recognized; treating as linker script
/usr/bin/ld:/usr/ports/www/node/work/node-v9.11.1/out/Release/obj.target/deps/v8/src/libv8_base.a:1: 
syntax error
c++: error: linker command failed with exit code 1 (use -v to see 
invocation)
deps/v8/src/mksnapshot.target.mk:155: recipe for target 
'/usr/ports/www/node/work/node-v9.11.1/out/Release/mksnapshot' failed
gmake[3]: *** 
[/usr/ports/www/node/work/node-v9.11.1/out/Release/mksnapshot] Error 1

gmake[3]: *** Waiting for unfinished jobs



FreeBSD puchar.net 11.1-STABLE FreeBSD 11.1-STABLE #1 r332001: Wed Apr  4 
12:52:01 CEST 2018 r...@puchar.net:/usr/src/sys/amd64/compile/puchar 
amd64



any idea?


___
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: Changing PHP default version from 5.6 to 7.2 timeframe?

[Carmel NY]

On Thu, 19 Apr 2018 17:51:51 +0200, Matthias Fechner stated:

>Am 19.04.2018 um 16:48 schrieb Kurt Jaeger:
>> I'm not involved in the decision, but I've heard from problems
>> with typo3 and php7.2.  
>
>I saw similar problems with other products.
>For me I will stick to php7.1 for at least one year, this version seems
>to be quiet stable to use.

I am using php-72 without any problems, with the exception of "phpldapadmin";
however, there is a version of that application available that has been updated
to work with the latest versions of PHP. I actually have it installed and
working perfectly, along with phpMyAdmin, ldap-account-manager and joomla3.

I set php72 as the default on my machine since time moves forward not
backwards and I like to keep current whenever possible.

As a foot note, newer versions of joomla3 and the soon to be released joomla4
are not supposed to be compatible with older versions of php. I have not
confirmed that however.

-- 
Carmel
___
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: Changing PHP default version from 5.6 to 7.2 timeframe?

[Matthias Fechner]

Am 19.04.2018 um 16:48 schrieb Kurt Jaeger:
> I'm not involved in the decision, but I've heard from problems
> with typo3 and php7.2.

I saw similar problems with other products.
For me I will stick to php7.1 for at least one year, this version seems
to be quiet stable to use.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Changing PHP default version from 5.6 to 7.2 timeframe?

[Guido Falsi]

On 04/19/18 16:48, Kurt Jaeger wrote:
> Hi!
> 
>> It appears that there is some work going on to prepare to switch
>> the default PHP version from 5.6 to an actively supported version.
> 
> Yes.
> 

Aren't php flavors going to somewhat make the point moot? I recently
added flavoring to the php-composer port, for example. It is now
available for any php version(in the latest packages, will trickle down
to quarterly).

PHP applications still need to be ported to flavors, it requires only a
little time.

Maybe I am missing something obvious.

-- 
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: Changing PHP default version from 5.6 to 7.2 timeframe?

[Kurt Jaeger]

Hi!

> It appears that there is some work going on to prepare to switch
> the default PHP version from 5.6 to an actively supported version.

Yes.

> What is the approximate timeframe for that change, if any?

I don't know.

> Should I jump and change the default version for my installs? I'm
> running the usual suspects like WordPress, MediaWiki, phpMyAdmin.

Yes, and please report if you find problems 8-} We need more
testers 8-)

> Looking at the supported versions page, I would expect the change be made to 
> 7.2.  Is that correct?

I'm not involved in the decision, but I've heard from problems
with typo3 and php7.2.

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

Changing PHP default version from 5.6 to 7.2 timeframe?

[Stefan Bethke]

It appears that there is some work going on to prepare to switch the default 
PHP version from 5.6 to an actively supported version.

What is the approximate timeframe for that change, if any?

Should I jump and change the default version for my installs? I'm running the 
usual suspects like WordPress, MediaWiki, phpMyAdmin.

Looking at the supported versions page, I would expect the change be made to 
7.2.  Is that correct?

http://php.net/supported-versions.php


Thanks,
Stefan


--
Stefan Bethke    Fon +49 151 14070811




signature.asc
Description: Message signed with OpenPGP

Re: saslauthd ldap connection to Samba AD

[Andrea Venturoli]

On 04/18/18 17:31, Jan Bramkamp wrote:
I use saslauthd with GSSAPI (aka Kerberos) authentication inside jails. 
IIRC you have to install a second package to add GSSAPI support to 
saslauthd.


Hello and thanks for your answer?

Which package would that be?

There is no other port mentioning saslauthd in the name apart from 
security/cyrus-sasl2-saslauthd.


There's security/cyrus-sasl2-gssapi: is this it?

 bye & Thanks
av.
___
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"