Re: USES=cargo vs. workspaces
On 06/05/21 18:32, Jan Beich wrote: > Did you try CARGO_GIT_SUBDIR? See > https://cgit.freebsd.org/ports/commit/?id=ab415159b8b9 > If that commit message is still unclear check existing consumers: Thanks, it worked! I wasn't aware of it. -- Alex Dupre ___ 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: USES=cargo vs. workspaces
On 07/10/19 09:41, Alex Dupre wrote: >> Some projects (e.g., Servo, Veloren) bundle several packages together. >> When dependencies also bundle packages it confuses "git" override. >> Any tips/workarounds that scale beyond 1 port? > > I haven't a solution, I can just say that I have the same issue with the > parity ethereum client (that in fact it's not in the ports tree yet). With the latest openethereum update, that adds the new rethutil dependency, the issue came up again: ===> Configuring for openethereum-3.2.5 error: failed to get `reth-util` as a dependency of package `ethcore v1.12.0 (/wrkdirs/usr/ports/net-p2p/openethereum/work/openethereum-3.2.5/crates/ethcore)` Caused by: failed to load source for dependency `reth-util` Caused by: Unable to update /wrkdirs/usr/ports/net-p2p/openethereum/work/reth-573e128487d5651f301e21faa97fc8e80f91dee8 Caused by: found a virtual manifest at `/wrkdirs/usr/ports/net-p2p/openethereum/work/reth-573e128487d5651f301e21faa97fc8e80f91dee8/Cargo.toml` instead of a package manifest ** Error code 101 Stop. make: stopped in /usr/ports/net-p2p/openethereum CC'ing freebsd-rust@ since they maintain the cargo stuff. Any help is appreciated. -- Alex Dupre ___ 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: FreeBSD Port: roundcube-php80-1.4.9,1
David Probst wrote: > I have successfully installed fully working late(st) versions Apache with PHP > support, dovecot, postfix and MySQL 8.x servers all happily doing the right > things and yet Roundcube will not connect to the database server regardless. > I even tried using MariaDB I still have no joy. There is something > fundamentally wrong yet no log files or any other information I can find on > the web has led me to overcome these last steps which has me somewhat > perplexed. The setup should be quite straight-forward, following just these two entries in the INSTALL file: 4. Create a new database and a database user for Roundcube (see DATABASE SETUP) 5. Point your browser to http://url-to-roundcube/installer/ Said so, you are using php8 and mysql8, and these versions can surely give some more headaches: 1) PHP 8: I don't think it's officially supported by roundcube, it may work but not 100% guaranteed 2) MySQL 8: it includes a change in the default authentication system that broke almost all php installations. To restore the old behavior a possibility is to use a my.cnf file with: [mysqld] default_authentication_plugin = mysql_native_password -- Alex Dupre ___ 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: Donation to Foundation for Poudriere /opt builds! (Bounty?)
Mason Loring Bliss wrote: > Hey all. I want to have Poudriere build packages that build and install to > /opt instead of /usr/local. I think you should use: PREFIX=/opt LOCALBASE=/opt -- Alex Dupre ___ 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: USES=cargo vs. workspaces
On 06/10/19 15:09, Jan Beich wrote: > Some projects (e.g., Servo, Veloren) bundle several packages together. > When dependencies also bundle packages it confuses "git" override. > Any tips/workarounds that scale beyond 1 port? I haven't a solution, I can just say that I have the same issue with the parity ethereum client (that in fact it's not in the ports tree yet). -- Alex Dupre ___ 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: Port with sbt build (archivers/snappy-java)
Alex Dupre ha scritto: The new version of snappy/java however seems to use an sbt build, which is quite different. Has anyone got any experience of porting anything with an sbt build. Another thing you can try: https://github.com/sbt/sbt-export-repo -- Alex Dupre ___ 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: Port with sbt build (archivers/snappy-java)
Mark Dixon ha scritto: The new version of snappy/java however seems to use an sbt build, which is quite different. Has anyone got any experience of porting anything with an sbt build. No experience, but have you seen this? https://github.com/sbt/sbt/wiki/User-Stories:--Offline-mode-and-Dependency-Locking -- Alex Dupre ___ 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: PHP 5.6 is default. What do lang/php5 users do?
Mike Brown ha scritto: From looking at the commits,[1] it seems that if I didn't have lang/php5 (5.4) installed, and then I installed something that requires PHP, I'd get lang/php56. Is that right? Yes. But since I do have lang/php5 installed, upgrading with 'portmaster php5' will just get me 5.4.38, not 5.6. Correct. So should I install lang/php56 myself now, If you like. or is it expected that lang/php5 will eventually become 5.6 and I should just wait, No. or what? You may also stay with php 5.4, it's your call. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: php55-5.5.19
Sascha A. Borer ha scritto: In the FreeBSD Port php55 I try to activate the extension intl.so Strangely, after compiling, there is no intl.so or php_intl.so available. Simply install devel/pecl-intl -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: poudriere and DISABLE_VULNERABILITIES
Russell L. Carter ha scritto: However, what I would like to learn is if poudriere is able to understand DISABLE_VULNERABILITIES=YES, and if so, how to enable it. I'm not asking a political question here, just a technical one. If this is possible, how do I do it? NO_IGNORE= yes -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: bundled libraries in ports, any policy?
René Ladan ha scritto: Although the above example is specific to Chromium, do we want a policy for bundled libraries in general? For example, Fedora an Gentoo have a policy that favors the use system libraries (what we call LIB_DEPENDS) Yes, we prefer always system/port libraries, if there aren't strong reasons to do otherwise (e.g. a highly customized bundled version) -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: WANT_PHP_WEB is just a synonym for WANT_PHP_CGI in automated build environments
Matthew Pounsett ha scritto:
It looks to me like the rules that WANT_PHP_WEB uses to decide whether to
build the CGI or module version of PHP will always choose the CGI version
unless the module is already installed. If this is true, it means that in
automated build environments (e.g. tinderbox) – where *only* the direct
dependencies of a port are installed at build time – there isn’t any way to
tell WANT_PHP_WEB to install the module. This effectively makes WANT_PHP_WEB
a synonym for WANT_PHP_CGI in these environments.
Have I missed something, or is this a significant flaw in the design of the
WANT_PHP_{WEB,CGI,MOD} knobs?
You missed the fact that you can install the php module as a separate
port/package together with the core php package. Not only, mod_php port
requires core php port, that is the one containing the cgi version. So
there isn't any problem with tinderbox/poudriere.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: USE_MYSQL / USE_PGSQL buildtime dependency differences
Miroslav Lachman ha scritto: I think there is no need to install MySQL server on the same machine with Icinga2 (or any other MySQL dependent port). It really needs client library and then it can connect to any remote MySQL server. That's why this is not supported by bsd.database.mk. Exactly. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: gcc vs gcc48
Sean Bruno ha scritto: Ended up in a weird position today running a build. My poudriere instance ended up building gcc and gcc48 at the same time. I thought this was odd. Shouldn't gcc48 supplant gcc for requirements? Every port is built independently from the others, so gcc48 is not found when building other ports that doesn't strictly require it. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: gcc vs gcc48
Sean Bruno ha scritto: This seems like a broken feature of ports IMO. I.e. non-consistent runs. It seems quite strange to me, poudriere shouldn't exhibits such behavior. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: gcc vs gcc48
Guido Falsi ha scritto: It is a bad feature of ports on a live system, poudriere avoids this...at least it should. It's not bad for ports on a live system, it's a feature to not install many gcc versions if you already have one that can satisfies all needs. Ports and packages have different needs. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: gcc vs gcc48
Guido Falsi ha scritto: I agree, but there is a consistency problem, different systems WILL behave differently, for a good reason though :) I'd add that currently if you are using ports instead of packages is because you WANT a different behavior ;-) -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: roundcube's switch to composer, anything plugin port maintainers should be doing?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Bethke ha scritto: I was in the process of upgrading a roundcube plugin (sauserprefs) and noticed that roundcube is switching/has swichted to composer. This is the first time I’ve come across composer. Should I ignore that for the moment? Is there work underway to convert the plugin ports to use composer? Should the plugin ports be removed in favor of using composer manually? Is composer production ready yet? Inquiring minds want to know… Hi Stefan, like you this is the first time I've come across 'composer'. It's a dependency manager, I have no plans to support it, you can ignore it for the moment. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlONwxgACgkQgRXp2M5fVU3XswCeLKaMnh4M+nh8FbEdFkjMp5Ny 0FwAn39S9AuaBzzezAE4XY3TAtoUSAJ7 =YSZ5 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Troubles upgrading RoundCube
Andrea Venturoli ha scritto:
While trying to upgrade RoundCube, it seems to look for php in the wrong
place:
Try the following patch and let me know:
Index: Mk/bsd.php.mk
===
--- Mk/bsd.php.mk (revision 351469)
+++ Mk/bsd.php.mk (working copy)
@@ -161,6 +161,8 @@
.endif
RUN_DEPENDS+= ${PHPBASE}/include/php/main/php.h:${PORTSDIR}/${PHP_PORT}
.if defined(WANT_PHP_MOD) || (defined(WANT_PHP_WEB)
defined(PHP_VERSION) ${PHP_SAPI:Mcgi} == ${PHP_SAPI:Mfpm} == )
+USE_APACHE=22+
+.include ${PORTSDIR}/Mk/bsd.apache.mk
RUN_DEPENDS+=
${PHPBASE}/${APACHEMODDIR}/libphp5.so:${PORTSDIR}/${MOD_PHP_PORT}
.endif
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: print/cups: since update to 1.7.1: error : Send-Document client-error-document-format-not-supported
Boris Samorodov ha scritto: Great, glad to be helpful. May be the patch is not right and the problem should be resolved in another way. But anyway the problem seems to be localized and I'm sure Max will do the right thing. As already said, I fixed the very same problem with hplip installing cups-filter: I don't know which one is the correct way. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PHP Warning: Unable to load dynamic library
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 O. Hartmann ha scritto: Since a couple of days by now I get bothered by this nasty error corrupting all the services provided via Apache24/PHP: [...] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20100525-zts/xsl.so' - Cannot open quot;/usr/local/lib/php/20100525-zts This happens to all .so libraries, apache24 want to load upon start. The path is /usr/local/lib/php/20100525, NOT /usr/local/lib/php/20100525-zts. I recompiled apache and all php stuff without option ZTS enabled to get rid of the wrong path, but it seems I didn't hit the culprit port. You did exactly the opposite of what you had to do. As the WARNING says, build lang/php5 with ZTS enabled and rebuild all extensions. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlNHrlwACgkQgRXp2M5fVU1WaQCeNAqH93QF5/uO9LhwucLUpJI3 HFUAn1T4KHDBUEngBE/QXEKG3RIwp85r =Z0li -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Why java/linux-sun-jdk18 added?
Koichiro IWAO ha scritto: java/linux-sun-jdk18 was added just now but isn't it identical to java/linux-oracle-jdk18 ? Why -sun- port is needed? It was removed 30 minutes after the commit :-) -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: print/hpijs + new cups + foomatic not working with hpijs-pcl3e printer.
Naram Qashat ha scritto: That worked fine with cups 1.5. With 1.7 the printer prints nothing. I guess something is broken. I have a mixed behavior, I can print e.g with okular, but not with seamonkey. With older cups, no problems. Anything suspicious at /var/log/messages, /var/log/cups/*? OS version and which cups / foomatic ports are installed? This is the cups error_log when printing from seamonkey: E [09/Apr/2014:10:19:33 +0200] [Client 14] Returning IPP client-error-document-format-not-supported for Print-Job (ipp://localhost:631/printers/HP_LaserJet_M1522nf_MFP) from localhost Something that I think needs to be brought up. It appears that since CUPS 1.6.x, cups-filters is required for it to work with most printers. I confirm that installing cups-filters restored correct behavior for all applications. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: can pkg install mod_php5 (ie. libphp5.so) ?
Saifi Khan ha scritto: Indeed PHP-FPM is a very useful approach since we dont need to worry about suexec or mod_php. This helps apache and php stock installations and packaging to evolve in a modular way. However, the 'ProxyPassMath' directive cannot be used on a Directory section. ProxyPassMatch Directive Context:server config, virtual host, directory -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: databases/mysql56-client build failure on 9.2-STABLE i386
Greg Rivers ha scritto: The recent update from mysql56-client-5.6.15 to mysql56-client-5.6.16 fails to build on 9.2-STABLE i386. It builds fine on amd64 (both 9.2-STABLE and 10.0-STABLE). Unable to reproduce, it builds fine also on my 9.2-i386 poudriere jail. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: openldap-client OPENSSL_CFLAGS
Marko Cupać ha scritto: I have problem building net/openldap24-client on 10-RELEASE amd64: === Building for openldap-client-2.4.38 make[2]: make[2]: don't know how to make OPENSSL_CFLAGS. Stop Should I send PR? Same issue with x11/kdelibs4, I think something is broken in the ports tree. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Where to find keywords for pkg-plist? (@mode, @group, ...)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: Is there a file in /usr/ports/Mk/* that shows all of the @ keywords that can be used in the pkg-plist? A simple grep didn't answer me. For instance, @mode sets the chmod file, @owner the user and such. man pkg-create or man pkg_create I cannot find anything in 'man pkg-create' about such keywords. They were explained in 'man pkg_create' but it's not installed anymore on newer FreeBSD releases. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlKwI1wACgkQgRXp2M5fVU0cAQCg5f2LlmcLQfKGGdvRss2axcXN VR4AnjW03QNbOZUnAtLH/dZcbIZ08Ugk =mf9k -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Where to find keywords for pkg-plist? (@mode, @group, ...)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: It is since pkg 1.2.2 Ops, sorry for the noise, I checked on a machine with an older 'pkg'. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlKwJpAACgkQgRXp2M5fVU2e0QCfVzdDdfuV/8Sce71aqHtpD8LU 8doAoLJAjb2I8v8XBuF6oJGkCPJQNsRj =2rRC -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Stage and /var ?
Thierry Thomas ha scritto: How should we stagify ports writing out of their $PREFIX for good reasons, e.g. a statedir like /var/foo/$PORTNAME. Usually such directories are created at runtime (perhaps by the startup rc script) and not during package installation. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Explain staging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: You should have received 2 mails from me with some details about staging: one called [HEADSUP] Stage support for the ports tree and on called Staging, packages and more (very recent as of yesterday) I think the issue was that such very first email was lost somewhere, as Stefan said there isn't in the mailing list archive, I've never received originally, but there a few replies to it. Can you resend it to the list, please? - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.21 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlJNIK4ACgkQgRXp2M5fVU2alACeJOFyKCxkhx82fc792dIie7cN OMcAoOnn0HvdURdcD8ToW6i4RHROqyGJ =1icY -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Explain staging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: Here you are: http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086346.html I was referring the the previous one: [HEADSUP] Stage support for the ports tree. Dunno if it had additional info or this second one is enough. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.21 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlJNMdAACgkQgRXp2M5fVU11iQCgmj+i9/UUJDKP1mdgAzAMYbO2 MD8AnRbMZ3rQr+K9SSyXDFgPg1JsvHrc =KChF -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postmaster php55 left php5 stuff
Bryan Drewery ha scritto: This is going to sound crazy, but I think the only safe way to upgrade major PHP versions currently is to deinstall all php ports, then install the new version/origins. That and other methods were discussed on ports@ when 5.4 came out. Yes, there are 10 types of people in the world: who want php port always updated to the latest branch and who want a new set of phpXX ports for every branch. It's impossible to satisfy both types, unless we keep an additional set of 'php' ports with the same contents of latest 'phpXX' set. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: NOCC and ctype
Andrea Venturoli ha scritto: Perhaps I picked it up in some unobvious way... or perhaps should it be added as a dependency? Fixed, added as dependency, thanks for reporting. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: lang/php55 and buildin opcode
Subbsd ha scritto: So, www/pecl-zendopcache is still necessary for lang/php55 when we need for zend opcode? Thanks You should use pecl-zendopcache for now, they are the same extension. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: switch lang/php5 to 5.5 - when?
cronfy ha scritto: Are there any estimates known about when lang/php5 will switch to php 5.5 version? In the last commit comment to lang/php55 it is marked as future step, but it is not evident when it will happen. Can someone clarify this? Never. The commit says lang/php5 will be removed / moved to lang/php54. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: rc.d scripts to control multiple instances of the same daemon?
Garrett Wollman ha scritto: I've looked around for examples of good practice to emulate, and haven't found much. The closest to what I want looks to be vboxheadless, but I'm uncomfortable with the amount of mechanism from rc.subr that it needs to reimplement. Are there any better examples? Basically there are two types of implementation with different pro/cons: profiles and symlinks. vboxheadless is in the first category, tomcat7 in the second one: http://svnweb.freebsd.org/ports/head/www/tomcat7/files/tomcat7.in?revision=307489view=markup -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Proposal: do not show up the dialog(1) by default?
Chris Rees ha scritto: I find such behavior very useful, I find annoying the above behavior. If the dialog will not pop-up if the only options are the global ones it'd be much better, IMO. The correct solution to this is to not add those to DEFINE. *If* this is the correct solution, why for months we said committers to add them to DEFINE and now we have 50% ports with them and 50% without? There should be a clear definitive statement on this subject. I don't have a strong preference, but we should choose oon the two: 1) not list them in DEFINE 2) if DEFINE contains only them, not show the popup -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Proposal: do not show up the dialog(1) by default?
Baptiste Daroussin ha scritto: A lot of people seems to be complaining about the configuration dialog popping up all the time. Probably because now every ports that list DOCS/EXAMPLES/NLS pop up the dialog? What if we change the default behaviour to not pop up the dialog each time there is a changed option but only when the user explicitly type make config? Just a proposal, please give your opinion. I find such behavior very useful, I find annoying the above behavior. If the dialog will not pop-up if the only options are the global ones it'd be much better, IMO. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD's PHP port incomplete; missing ftp_ssl_connect function
Mark Felder ha scritto:
The problem is that the way FreeBSD handles PHP -- complete
modularization -- breaks the FTP module. The FTP module cannot be built
with support for FTPS unless it is built statically into PHP along with
OpenSSL. You can test this yourself by running the following command:
php -r 'if(function_exists('ftp_ssl_connect')) {echo ftp_ssl_connect
exists\n;} else {echo ftp_ssl_connect does not exist\n;}'
And my output is:
ftp_ssl_connect exists
Actually you can get a ssl-enabled php5-ftp in a very simple way: build
php5-ftp after php5-openssl.
Said so, such behavior should be harmonized, probably you could get a
ssl-enabled php5-ftp even without php5-openssl. I'll work on a patch.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD's PHP port incomplete; missing ftp_ssl_connect function
Alex Dupre ha scritto: Said so, such behavior should be harmonized, probably you could get a ssl-enabled php5-ftp even without php5-openssl. I'll work on a patch. After checking, I saw that it was already so in the past. A recent update broke it, but I've just fixed it. You don't need neither php5-openssl or anything compiled statically. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD's PHP port incomplete; missing ftp_ssl_connect function
Mark Felder ha scritto: That makes total sense but I never experimented further after seeing the official PHP response saying you have to do it statically and seeing what other Linux distros were doing. Sometimes official PHP responses are crap or don't apply to FreeBSD. However, this would still exclude cleanroom package building environments like poudriere or tinderbox, correct? Just fixed, now it always build a ssl-enabled php5-ftp without requiring php5-openssl. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: www/apache24: ports like lang/php5 or devel/subversion are disturbed by the apache24 port!
Olli Hauer ha scritto:
It will take a while until php is really apache24 ready.
Work is in progress on php upstream.
One of the issues is that APXS does not provide the
MPM model which is needed for php and others to build.
Can you try the following patch, please?
Index: bsd.php.mk
===
--- bsd.php.mk (revision 315696)
+++ bsd.php.mk (working copy)
@@ -60,9 +60,8 @@
HTTPD?= ${LOCALBASE}/sbin/httpd
.if exists(${HTTPD})
-APXS?= ${LOCALBASE}/sbin/apxs
-APACHE_MPM!=${APXS} -q MPM_NAME
-. if ${APACHE_MPM} == worker || ${APACHE_MPM} == event
+APACHE_THR!=${HTTPD} -V | ${GREP} threaded
+. if ${APACHE_THR:Myes}
PHP_EXT_DIR:= ${PHP_EXT_DIR}-zts
. endif
.elif defined(APACHE_PORT) (${APACHE_PORT:M*worker*} != ||
${APACHE_PORT:M*event*} != )
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: LEGAL variable to capture generic issues
Eitan Adler ha scritto: I have been trying to capture the differences between LEGAL and the ports tree. At this point I am convinced we need a new variable to capture in a machine usable way issues such as special permission granted to distribute under the GPL or No license -- see http://cr.yp.to/softwarelaw.html;. Furthermore some ports define NO_PACKAGE for reasons of legality (GPL issues) and others defined it for other reasons (the package becomes too big). We have no method to differentiate between these two reasons. For license reasons we already have this: # RESTRICTED- Prevent the distribution of distfiles and packages to # the FTP sites or on CDROM (e.g. forbidden by license # considerations). and related /usr/ports/LEGAL entries. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: LEGAL variable to capture generic issues
Eitan Adler ha scritto: RESTRICTED does not cover special permission granted to distribute and other not-a-restriction things. And why do we need them? RESTRICTED is for !distributable, exactly as the LEGAL file. We can improve RESTRICTED to automatically generate LEGAL. For particular licenses we already have a controversial LICENSE framework. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: LEGAL variable to capture generic issues
Eitan Adler ha scritto: The LEGAL file is for a broader set of things than just RESTRICTED. It covers no commercial use which is NO_CDROM but not RESTRICTED Yup, LEGAL is both NO_CDROM and RESTRICTED, and RESTRICTED_FILES already contains the list of !distributable files. I'd say this is enough for generating LEGAL (modulo correct use of these knobs). -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: LEGAL variable to capture generic issues
Eitan Adler ha scritto: This is insufficient to include, say, line 212: raknet-*devel/raknetOriginal license is Indy license, special authorization granted to provide RakNet under GPL v3 Ehmm, I could argue about the private email permission, but if it's listed in LEGAL it should be marked as RESTRICTED or NO_CDROM, otherwise it should not listed there (the LICENSE framework already says that special authorization has been granted). -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ${PORT_OPTIONS:MDOCS}
Carmel ha scritto:
I have a problem with updating a Makefile for an existing port. When
running portlint -a on the Makefile, it pops up with this warning:
WARN: Makefile: [53]: NOPORTDOCS found. Consider using
PORT_OPTIONS:MDOCS
So, I have tried doing what the Porters Handbook suggested, and it just
bombs out with this useless message:
You should add:
.include bsd.port.options.mk
before checking for ${PORT_OPTIONS:MDOCS}
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: update failed for security/nss-3.14.3
Andrew W. Nosenko wrote: Jan committed a patch that should work, is that an acceptable workaround for your use case (it pulls in a newer gcc)? Can you test it and report back? Yes, it works correctly, thanks. Sorry, but it doesn't work for my FreeBSD-8.0. The gcc-4.2 from base (under name 'cc') is used anyway with the same error The patch was actually committed to the FreeBSD ports tree only recently (18 hours ago). Are you sure you have it? -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: update failed for security/nss-3.14.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Florian Smeets wrote: Jan committed a patch that should work, is that an acceptable workaround for your use case (it pulls in a newer gcc)? Can you test it and report back? Yes, it works correctly, thanks. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlEl6woACgkQgRXp2M5fVU1p/wCfQ1SU4Amt32LsAaEUReUgGQHx VgIAoPxH6sr9jO9o3Fam8Q1U16xQiQoz =2fF4 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: update failed for security/nss-3.14.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 joerg_surmann wrote: hi all, can't update security/nss. INTEL_GCM option of nss is quite flawed. ifdef INTEL_GCM # # GCM binary needs -mssse3 # $(OBJDIR)/$(PROG_PREFIX)intel-gcm-wrap$(OBJ_SUFFIX): CFLAGS += -mssse3 # The integrated assembler in Clang 3.2 does not support % in the # expression of a .set directive. intel-gcm.s uses .set to give # symbolic names to registers, for example, # .set Htbl, %rdi # So we can't use Clang's integrated assembler with intel-gcm.s. ifneq (,$(findstring clang,$(AS))) $(OBJDIR)/$(PROG_PREFIX)intel-gcm$(OBJ_SUFFIX): ASFLAGS += - -no-integrated-as endif endif It requires -mssse3 flag, so it cannot be built on 8.x with base gcc: cc1: error: unrecognized command line option -mssse3 It uses assembly code not recognized by clang. I'd say we should disable it to start. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlEkowMACgkQgRXp2M5fVU0CmQCfRWC2jiKHHTXTx4bbCNqnhcF0 gWAAni78byI4KTAPEklHzEJviGMbG/yu =w+iQ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: update failed for security/nss-3.14.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Florian Smeets wrote: It works fine on anything = 8.3. Packages are usually built on N.0 releases and in fact my tinderbox with 8.2-RELEASE fails with: cc1: error: unrecognized command line option -mssse3 - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlEk/zsACgkQgRXp2M5fVU3H1gCgukHYNN0FovIhsgfazqy8OLtf gRYAn1baFa+4YjVLa90MpLpjAsWk7jR8 =4u6z -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: update failed for security/nss-3.14.3
Florian Smeets ha scritto: No, they are built on the last supported N.X which is 8.3 right now. 8.2 is out of support for almost 7 months. I don't mind including a patch to make it work on 8.2, but I don't have time (and motivation) to spend on an unsupported release. Ok, maybe I'll work on a patch tomorrow. I think the patch should simply disable building INTEL_GCM on FreeBSD 8.3, correct? -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mysql 5.6 port
Domas ha scritto: Is there any time frame known when MySQL 5.6 port will be available ? Nope, I'm working on it, but no ETA. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Breaking out gcc-ecj45 from lang/gcc{,46,47,48}
Gerald Pfeifer ha scritto: to address ports/175072 I finally went ahead with an old plan of mine and broke the binary ecj.jar that is used to build the Java frontend for our GCC 4.6, 4.7 and 4.8 ports out into a separate port: lang/gcc-ecj45. Why not using/updating the java/eclipse-ecj port? -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: USE_MYSQL
Helmut Schneider ha scritto: what does USE_MYSQL=yes do, require mysql-server, or mysql-client? If mysql-client, how can I depend on the server (or v.v.)? From bsd.database.mk: # USE_MYSQL - Add MySQL (client/server/embedded) dependency (default: # client). -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] databases/mariadb55-{server|client} ports
Alexandr Kovalenko ha scritto: Basically I'm for having both mysql and mariadb ports semi-identical - have same install layouts, so if you feel that layout you are using in mysql55-* is better - it is easy to fix so that mariadb55 will resemble it. I don't say it's better in absolute terms, I say it's like in linux distros, so we are giving a coherent and consistent behavior. It's a tradeoff. P.S. I've also noticed that you have .conf file in bin/mysqlaccess.conf in mysql55-client - was that intentional? Shouldn't it be placed somewhere like /usr/local/etc ? The reason is exactly the same as before, but yes, in this particular case it may not be the best decision (probably not installing it at all would be better). -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] databases/mariadb55-{server|client} ports
Alexandr Kovalenko ha scritto: Fixed pkg-plist bug with libmysqlservices.a (which, btw, should be fixed in mysql55-client too - libmysqlservices.a should not be installed in any of packages). Why do you say so? libmysqlservices.a is needed to create plugins. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] databases/mariadb55-{server|client} ports
Alexandr Kovalenko ha scritto: At least it should be installed with server package, not client. It is installed together with headers needed to build plugins. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] databases/mariadb55-{server|client} ports
Alexandr Kovalenko ha scritto: Thanks for noticing this. I'll submit another PR after this one is commited to remove those headers from -client and add to -server, will also re-add libmysqlservices.a to -server together with headers. Why are you going to hack the mariadb ports is such way? The MySQL 5.5 ports are so for a reason. From the original commit log: - new installation layout, resembling RPM packages: - client = Client Utilities + Development Libraries + Shared components - server = MySQL Server + Embedded -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Notes on upgrades after libpcre update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tijl Coosemans ha scritto: It says that the new shared lib is compatible with the old lib (only new interfaces were added), since: 1 - 0 = 3 - 2 = 1 1 - 0 = 2 - 2 = 0 Ops, the last should be 0 - 0 obviously. (from the [current:revision:age] version = current - age rule) This should be mandatory knowledge for every ports committer. Yes, it should. It's explained here: http://www.freebsd.org/gnome/docs/gnome_porting.html Not much visible or clear that it's not limited to gnome ports. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDJqY4ACgkQgRXp2M5fVU0b9ACg6w3eHCpLMRK6088l+dSIJ8CZ HB0AoKcxHQn3MlkURZuHUyxcV3iKofto =aEoz -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC/HEADSUP] portmaster default -w (preserve shared libraries)
Kurt Jaeger ha scritto: I have a few question about what happens if you always use this flag: * Do you keep every version of the shlibs you ever built on your system? No, only those that still needed. * Are there any method to clean the unused ones? sysutils/libchk or pkg_libchk from sysutils/bsdadminscripts. Uh? One of the two: 1) it keeps all versions and you need to clean them up 2) it keeps only needed and so you shouldn't clean up The correct answer is 1) -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Notes on upgrades after libpcre update
Kevin Oberman ha scritto: As many of you noticed, the update of devel/pcre bumped hte version of libpcre.so which is a dependency of LOTS of things. This was a very poor choice, we shouldn't have bumped the version. When there is a bump between two minor releases (8.31 - 8.32) a red led should blink in port maintainer. The port should have defined: USE_AUTOTOOLS= libtool USE_GNOME= ltverhack to avoid bumbing the version. In fact this is the diff in configure.ac: -m4_define(libpcre_version, [1:1:0]) -m4_define(libpcre16_version, [0:1:0]) +m4_define(libpcre_version, [3:0:2]) +m4_define(libpcre16_version, [2:0:2]) It says that the new shared lib is compatible with the old lib (only new interfaces were added), since: 1 - 0 = 3 - 2 = 1 1 - 0 = 2 - 2 = 0 (from the [current:revision:age] version = current - age rule) -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC/HEADSUP] portmaster default -w (preserve shared libraries)
Kevin Oberman ha scritto: The main reason for keeping the libraries is that it reduces the number of breakages during the upgrade process, which can be a very serious inconvenience, particularly if the forced update fails to complete. In my experience the problem you describe is much less significant. It does eliminate the instant breakage of lots and lots of stuff, but it can lead to hard to track down issues later. Exactly. Moreover the pcre version bump was not necessary, we created a problem where it wasn't. I'd say that when there are shared library bumps the commits should be checked and reviewed by multiple eyes. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC/HEADSUP] portmaster default -w (preserve shared libraries)
Jeremy Messenger ha scritto: Absolutely yes from me. The -w option is real lifesaver and should be on by default. I disagree. The -w is a temp fix and not a correct solution, so it shouldn't be default. I agree with your disagreement :-) -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC/HEADSUP] portmaster default -w (preserve shared libraries)
Chris Rees ha scritto: I get what you're saying, but please consider which is easier to reverse- deleting an accidentally saved library, or restoring an accidentally deleted library? Unluckily it's not so simple... Defaults should be safe. I was bitten by this with pcre- sometimes we can't update all our ports at one time. How isn't it correct? For simple ports it may works correctly, but for others it could happen that finally both revisions are linked into a library or executable (because one !recompiled dependency depends on the old version and another recompiled dependency depends on the new version) and this is not good. So the correct thing is to always recompile ports to get the new version, the 'keep old libs' flags should be used with caution (this is why I prefer it to be opt-in and not opt-out). We still keep src libraries around until we make delete-old-libs. Why should ports be different? Also for src the policy is: don't recompile any ports after an upgrade, or recompile them all, exactly for this reason. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [BRAINSTORMIG] name of the variable for passing command line options via make
Olli Hauer ha scritto: WITH / WITHOUT I thought this was a joke, but thinking about it, this is the best idea IMO. I agree, but silently thinking OH NO! this brings us back to the discussions from a view months ago... If I understand correct the LATE_(UN)SET parameter can be used inside the port after including bsd.port.options.mk (where I really miss it) and CMD_(UN)SET from the command line. Hmm, no, I've understood that they are simply two different proposals for the same features, i.e. command line overriding. I vote for WITH / WITHOUT. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: RUN_DEPENDS=: not respected? Bug?
O. Hartmann ha scritto:
Working on a small port for OpenCL support for CPUs via freeocl,
I run into a problem (runing FreeBSD 10.0-CURRENT).
The port requires devel/libatomic_ops, which installs a static library
/usr/lcoal/lib/libatomic_ops.a.
Following the instructions in the Porter's Handbook for FreeBSD, I added
a line
RUN_DEPENDS=
${LOCALBASE}/lib/libatomic_ops.a:${PORTSDIR}/devel/libatomic_ops
It seems strange to me that a port requires a static library at runtime.
You should use BUILD_DEPENDS if the library is needed to build the port.
And you shouldn't put if after inclusion of bsd.port.pre.mk.
RUN_DEPENDS is for things required at runtime and so usually installed
in the install step.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
Baptiste Daroussin ha scritto: On of the thing I forgot and kan@ has added is a prompt for the user in case it is going to bootstrap. So, removing the prompt will make everybody happy? :-) What about a prompt with timeout? This is the first time pkg is run, I'll start bootstrapping in 10 seconds. Press CTRL-C now to abort -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
eacclerator and php 5.4
If you are interested in eaccelerator with php 5.4, please try the following patch and report success/failure. http://www.alexdupre.com/eaccelerator.diff -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: thunderbird-enigmail-1.4.3 build failing on i386 9.1
Doug Barton ha scritto: This problem is caused for portmaster by the wacky way that they changed the dependency for thunderbird sources to avoid (zomg!) potential for fetching files related to thunderbird during the enigmail build process. I objected at the time, but my objection was ignored. If you can feel better, I never approved it. OTOH, the recent enigmail update worked for me using portmaster, I haven't had time to investigate why it worked this time either. :) Because I put that horrible FETCH_DEPENDS inside a conditional :-) -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: editors/libreoffice : patches for 8.3-STABLE (i386)
Luca Pizzamiglio ha scritto: I'm Luca and my system is a 8.3-STABLE system (then with clang derived from ports) on a i386 architecture. I had problem to build the latest libreoffice (3.5.4), so I tried to solve issues I met and I developed this easy patches. Are they acceptable? Are this problem known also on other systems/architectures? They are partially correct (removing the offending 'case' is not correct). I have additional patches to also fix build with kde4 that are running on my tinderbox now. Talk to you later. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: seamonkey-2.9.1_1
Beat Gaetzi ha scritto: Yes, to get SeaMonkey 2.10.1 running we need to change parts of bsd.gecko.mk which affects other ports and this needs more testing. Is such path available somewhere? -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] Seeking Approval: include bsd.port.pre.mk so SRC_BASE is defined before referenced
Jason Helfman ha scritto: I am working on the following pr, and would like to get others approval to the following patch: http://people.freebsd.org/~jgh/files/pre-patch.txt This patch is fixing several use cases of SRC_BASE before it is defined. I don't agree for the quantis-kmod patch. I think simply removing SRC_BASE?= line is the correct fix. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP] New framework options aka optionng
Erwin Lansing ha scritto: portmgr has been working for long on a new option framework for the ports to improve some of the deficiencies in the current framework. Great work! Looking quickly at the documentation I have a doubt: while I think most ports handle NOPORTDOCS, I think WITHOUT_NLS is handled only by a small percentage, so, if I have understood correctly, many ports should include OPTIONS_EXCLUDE=NLS. Is it correct? -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PHP 5.4.0 : lang/php54
Svyatoslav Lempert ha scritto: FreeBSD 8.3 is done, please commit update lang/php5 to PHP 5.4 to portstree. Thank you in advance. I'm just waiting for final release of suhosin (both patch and extension) to commit the update. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Time to kill php4, who stands up to save it?
Chris Rees ha scritto: On a tangential issue, php52 should probably be kept around, at least for now. The PHP maintainer disagreed on this point last week-ish. Eh?! I never said it. It' fine to keep a maintained (not by me) php52, since php5 will be updated to 5.4 branch. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: About PHP 5.X in FreeBSD port tree
James Chang ha scritto: Thanks for your notice, but there seems no information about whether the vulnerabilities about CVE-2011-2483, CVE-2011-4153 and CVE-2011-3389 were fixed in FreeBSD port tree (PHP 5.3.10_1) or not? PHP 5.3.11 will be released soon and the port will be updated to this release before switching to (probably) 5.4.1. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
bouncycastle poll
Brief history: BouncyCastle 1.45 is the last release implementing APIv1. BC 1.46 and 1.47 are preliminary releases for next BC 2.0 that implement APIv2. The APIs are incompatible (and conflicting) and we need to keep both versions in the ports tree. Possible solutions: 1) repocopy java/bouncycastle into java/bouncycastle145 and update the former to 1.47 (and later to 2.0) 2) repocopy java/bouncycastle into java/bouncycastle1 and update the former to 1.47 (and later to 2.0) 3) repocopy java/bouncycastle into java/bouncycastle2 and update the latter to 1.47 (and later to 2.0) Which one do you prefer? -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: apache-2.4.X php5-5.4.X
alexus wrote: slightly off topic yet still _VERY_ important peace and _VERY_ widely used is mod_php. I know that was discussed about million times through mailing lists and other ways Exactly, so why are you jumping on for the million and one time? If you want custom packages set up your own tinderbox or package builder machine. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PHP 5.4.0 : lang/php54
Mr Dandy wrote: May be more correctly set PHP 5.4 by default to lang/php5, and repocopy current lang/php5 into lang/php53? Probably current maintainer of php (@ale) has the plan ;) I've already created patches to update the current php5 port to 5.4. I'm waiting for fixes to other main php-related ports and the end of ports freeze to make them public and then commit them. I'm tired to listen at every PHP release that we should not update because everything broke (and on the other side people asking me when the port will be update, because it has incredible new features). Updating php port is a big task and will be done with the correct timing. Functions removed in php5.4 have been deprecated 10 year ago, if you still rely on them after more than 2 years PHP 5.3.0 has been released, then probably you should stick to lang/php52 port, or find a maintainer and a committer willing to create and maintain lang/php53. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: libtool question again
Roman Bogorodskiy wrote: USE_AUTOTOOLS= libtool USE_GNOME= ltverhack to avoid bumping. I'm using it and it doesn't help: libgnutls.so.47 becomes libgnutls.so.48 (where 48 is 'current'). Probably you have not set LIBTOOLFILES to include all the 'configure' scripts. In any case, a bump will be necessary, because the shared version number will decrease, but at least it won't be necessary next times. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: libtool question again
Roman Bogorodskiy wrote: I'm planning to update security/gnutls from 2.12.16 to 2.12.17. A new interface has been added and the shared library version was updated accordingly: current was incremented and revision set to 0, just like the libtool documentation suggests: And 'age' ? If only a new interface has been added, age should be incremented too, and so the shared library bump is not needed. If so, you can use: USE_AUTOTOOLS= libtool USE_GNOME= ltverhack to avoid bumping. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: recent portrevision bump for libvpx
Andriy Gapon wrote:
Needless to say that all these ports got their port revisions bumped.
Was there a good reason for that? I don't know.
I just know that now I need to needlessly reinstall/rebuild about a hundred
ports, many of which are not quite light-weight.
It's time to experiment seriously with ${EXPLICIT_PACKAGE_DEPENDS} and
libtool patch to not link to indirect dependencies (ports/104877).
Ideally a port should include in LIB_DEPENDS all the direct dependencies.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: recent portrevision bump for libvpx
Alex Dupre wrote: Ideally a port should include in LIB_DEPENDS all the direct dependencies. And consequentially it should be bumped *only if* a direct dependency has a library version bump. With the current link to all attitude, we are never sure what need to be bumped, because of hidden dependencies, and so portmaster -r and similar approaches are always recommended in addition to probabilistic portrevision bumps. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
tinderbox question (Was: Re: recent portrevision bump for libvpx)
Alex Dupre wrote: And consequentially it should be bumped *only if* a direct dependency has a library version bump. This doesn't solve the fact that in 3 days my tinderbox has rebuilt nearly all ports 4 times. Is there a way to say tinderbox to not rebuild every ports (without portrevision bump) that depends on a just rebuilt port? -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: recent portrevision bump for libvpx
Alexander Leidinger wrote: When I made the EXPLICIT_PACKAGE_DEPENDS patch, I noticed that there is not only libtool at fault (reaction of the libtool developers was IIRC: it's not trivial to fix known problems for the cross-building case (for libtool-1.x?)), but also pkg-config and similar things Yes, I know, it's correct what you say, but this doesn't prevent to improve things. I'm not saying that tomorrow we'll have a perfect ports tree where all and only direct dependencies will be listed, but if we don't even start... Currently we have exactly the opposite case: ports that have direct (maybe not needed) dependencies to libraries that are not recorded in Makefiles. This is the root cause of portmaster -r or aggressive bumps. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: recent portrevision bump for libvpx
Matthew Seaman wrote: Adding code to run ldd(1) against the files installed by the port and processing the results shouldn't be too hard. This could be an idea for ports maintainers, to verify if LIB_DEPENDS is set correctly, but cannot be used as its generic replacement. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mysql 5.5 fails to build.
Martin Wilke wrote: I facing since a while on all my servers that mysql 5.5.20 fails to build. Have anyone of you seen something like that, Nope, sorry. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: php5 broken by commit from yesterday?
Steven Hartland wrote: I suspect the change meant to add this additional fix to the Makefile patch but instead replaced it. Damn, yes, right. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What use is WWWDIR_REL?
Doug Barton wrote: So this leads me to many questions, the first and most obvious of which is, what the heck good is WWWDIR_REL in the first place? I don't follow you: in what sense WWWDIR_REL is different from, e.g., DOCSDIR_REL or DATADIR_REL? Why do you want to remove it and not the others? -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Apache/web ports advice in TPH
Philip M. Gollucci wrote: This section: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/using-php.html is out of date, as the very first bit mentions a bunch of old apache stuff. I'm happy to help update it if someone can say authoritatively what should be there. You'll have to ask ale@ about php. Well, I'd say the only error about php is the default version, that's not 4 anymore, but 5. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Apache/web ports advice in TPH
Doug Barton wrote: I'm also curious about the advice to install stuff into /usr/local/www/appname. I vaguely remember that this was deprecated but it seems to still be true. I'm not aware of any deprecation, all my webapp ports install into www/appname. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Apache/web ports advice in TPH
Doug Barton ha scritto:
# Default: ${PREFIX}/www/${PORTNAME}
I went with ${WWWDIR} in the Makefile/plist so hopefully that will
future-proof it in the event of a change.
Yup, I meant WWWDIR with www/appname.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Weird conflict between libungif and giflib
Doug Barton ha scritto: Other than the mismatched checksums I haven't noticed any actual problems, so this is more of an Is this a problem? question. AFAIK all ports should switch to giflib and libungif should be removed from the tree. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Weird conflict between libungif and giflib
Doug Barton ha scritto: Well 2 of the ports that I have on my desktop that were using it are mine, so if it's agreed that this is the right direction to go I'm happy to update. I just tested them and they seem to work fine. Do it, please. If I remember correctly danfe@ proposed himself to do it for all the ports depending on libungif a few weeks ago ;-) -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: databases/mysql55-server and DISABLE_CONFLICTS
Marco Steinbach ha scritto: shouldn't I be able to fetch distfiles for conflicting ports, if DISABLE_CONFLICTS is set ? Yes, but in this case you should also set -DNO_IGNORE -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: multimedia/zoneminder: rc script runs mysql commands?
Boris Samorodov ha scritto: Actually this should not happen. mysql rc script has a poststart directive to wait until the daemon is up and running. Last time I used the port (zoneminder) a year ago. It was the case. Has something changed in a year? MySQL rc script was patched 3 years ago. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: multimedia/zoneminder: rc script runs mysql commands?
Boris Samorodov ha scritto: The problem is: while start-up zoneminder is launched after mysql was started but is not responding yet. Actually this should not happen. mysql rc script has a poststart directive to wait until the daemon is up and running. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Feasibility of splitting out web components of lang/php5
Doug Barton ha scritto: What would make my life a whole lot simpler is if lang/php5 were the command line version, and the cgi and apache modules were separate ports. Is this feasible? Short answer: no. Long answer: nothing is impossible ;-) Extensions are compiled based on settings of the core php. If you split core php in different ports, you end up with possibly many different settings (e.g, standard CLI, debug CGI, threaded mod_php) and so it's impossible to compile extensions that work for all SAPIs. In an ideal world, the core php should compile only a shared library, and the various SAPIs should link it. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: enigmail-thunderbird: problem with importing pgp key from keyserver
Andriy Gapon ha scritto: Anyone else can reproduce this? Have you updated to 1.3.4 release? https://www.mozdev.org/bugs/show_bug.cgi?id=24568 -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
