Re: Input on most correct way to set IS_INTERACTIVE for Postfix ports
On 08/02/2012 00:06, Doug Barton wrote: Couldn't you add an OPTION for updating mailer.conf? Then, if that OPTION is set, update mailer.conf; and if it isn't set, then leave mailer.conf alone. On my package-building system I do not want to twiddle mailer.conf, but on the systems that I install the package on, I do. I've often felt that having options that could be set at package install time might be a good idea. For instance, being able to achieve the same effect as NOPORTDOCS or NOPORTEXAMPLES without having to build a custom package. Or in the case of one of my ports, phpmyadmin, most of the options are purely to manipulate RUN_DEPENDS and control installation of php module dependencies that the software can optionally use if present. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
INDEX build failed for 7.x
INDEX build failed with errors: Generating INDEX-7 - please wait.. Done. make_index: p5-Params-Validate-1.03: no entry for /usr/ports/devel/p5-Module-Implementation make_index: p5-Params-Validate-1.03: no entry for /usr/ports/devel/p5-Module-Implementation Committers on the hook: cy delphij dinoex dougb eadler jgh osa pgollucci sbz scheidell sunpoet swills wen Most recent CVS update was: U MOVED U UPDATING U audio/rubygem-ogginfo/Makefile U audio/rubygem-ogginfo/distinfo U comms/rubygem-callsign/Makefile U comms/rubygem-callsign/distinfo U databases/memcached/Makefile U databases/memcached/distinfo U databases/p5-DBIx-Class-Schema-Loader/Makefile U databases/p5-DBIx-Class-Schema-Loader/distinfo U databases/p5-DBIx-Custom/Makefile U databases/p5-DBIx-Custom/distinfo U databases/ruby-bdb1/Makefile U databases/ruby-bdb1/files/patch-delegate U databases/ruby-bdb1/files/patch-super U databases/rubygem-activemodel/Makefile U databases/rubygem-activemodel/distinfo U databases/rubygem-activerecord/Makefile U databases/rubygem-activerecord/distinfo U databases/rubygem-arel/Makefile U databases/rubygem-arel/distinfo U devel/Makefile U devel/p5-AnyMQ/Makefile U devel/p5-AnyMQ/distinfo U devel/p5-CPAN-Meta-YAML/Makefile U devel/p5-CPAN-Meta-YAML/distinfo U devel/p5-Devel-CallChecker/Makefile U devel/p5-Devel-CallChecker/distinfo U devel/p5-Devel-CallChecker/pkg-descr U devel/p5-Devel-CallChecker/pkg-plist U devel/p5-DynaLoader-Functions/Makefile U devel/p5-DynaLoader-Functions/distinfo U devel/p5-DynaLoader-Functions/pkg-descr U devel/p5-DynaLoader-Functions/pkg-plist U devel/p5-Inline/Makefile U devel/p5-Inline/distinfo U devel/p5-Moose/Makefile U devel/p5-Moose/distinfo U devel/p5-Object-Simple/Makefile U devel/p5-Object-Simple/distinfo U devel/p5-Params-Validate/Makefile U devel/p5-Params-Validate/distinfo U devel/p5-Params-Validate/pkg-plist U devel/p5-Pod-Coverage/Makefile U devel/p5-Pod-Coverage/distinfo U devel/p5-Pod-Coverage/pkg-plist U devel/p5-Version-Requirements/Makefile U devel/p5-Version-Requirements/distinfo U devel/rubygem-activesupport/Makefile U devel/rubygem-activesupport/distinfo U devel/rubygem-coffee-rails/Makefile U devel/rubygem-coffee-rails/distinfo U devel/rubygem-delayed_job/Makefile U devel/rubygem-delayed_job/distinfo U devel/rubygem-facets/Makefile U devel/rubygem-facets/distinfo U devel/rubygem-hoe/Makefile U devel/rubygem-hoe/distinfo U devel/rubygem-interact/pkg-descr U devel/rubygem-json/Makefile U devel/rubygem-json/distinfo U devel/rubygem-json_pure/Makefile U devel/rubygem-json_pure/distinfo U devel/rubygem-kgio/Makefile U devel/rubygem-kgio/distinfo U devel/rubygem-logging/Makefile U devel/rubygem-logging/distinfo U devel/rubygem-method_source/Makefile U devel/rubygem-method_source/distinfo U devel/rubygem-method_source/pkg-descr U devel/rubygem-minitest/Makefile U devel/rubygem-minitest/distinfo U devel/rubygem-orm_adapter/Makefile U devel/rubygem-orm_adapter/distinfo U devel/rubygem-pry/Makefile U devel/rubygem-pry/distinfo U devel/rubygem-pry/pkg-descr U devel/rubygem-rake-compiler/Makefile U devel/rubygem-rake-compiler/distinfo U devel/rubygem-require_all/Makefile U devel/rubygem-require_all/distinfo U devel/rubygem-rspec/Makefile U devel/rubygem-rspec/distinfo U devel/rubygem-rspec-core/Makefile U devel/rubygem-rspec-core/distinfo U devel/rubygem-rspec-core/pkg-descr U devel/rubygem-rspec-expectations/Makefile U devel/rubygem-rspec-expectations/distinfo U devel/rubygem-rspec-mocks/Makefile U devel/rubygem-rspec-mocks/distinfo U devel/rubygem-rubigen/Makefile U devel/rubygem-rubigen/distinfo U devel/rubygem-sequel/Makefile U devel/rubygem-sequel/distinfo U devel/rubygem-sexp_processor/Makefile U devel/rubygem-sexp_processor/distinfo U devel/rubygem-slop/Makefile U devel/rubygem-slop/distinfo U devel/rubygem-slop/pkg-descr U devel/rubygem-sprockets/Makefile U devel/rubygem-sprockets/distinfo U devel/rubygem-tins/Makefile U devel/rubygem-tins/distinfo U devel/rubygem-uuid/Makefile U devel/rubygem-uuid/distinfo U devel/rubygem-yajl-ruby077/Makefile U devel/rubygem-yajl-ruby077/distinfo U devel/svnmerge/Makefile U editors/emacs.app/Makefile U editors/emacs.app/files/patch-src-filelock.c U mail/py-spf/Makefile U mail/py-spf/distinfo U mail/rubygem-actionmailer/Makefile U mail/rubygem-actionmailer/distinfo U mail/rubygem-mail/Makefile U mail/rubygem-mail/distinfo U net/rubygem-amqp/Makefile U net/rubygem-amqp067/Makefile U net/rubygem-open-uri-cached/Makefile U net/rubygem-open-uri-cached/distinfo U net-mgmt/hawk/Makefile U net-mgmt/hawk/pkg-plist U science/p5-Geo-BUFR/Makefile U science/p5-Geo-BUFR/distinfo U security/Makefile U security/binwalk/Makefile U security/binwalk/distinfo U security/binwalk/pkg-descr U security/libssh2/Makefile U security/libssh2/files/patch-src__libgcrypt.c U security/rubygem-net-ssh/Makefile U security/rubygem-net-ssh/distinfo U sysutils/44bsd-more/Makefile U sysutils/rubygem-backup/Makefile U sysutils/rubygem-backup/distinfo U
Re: [CFT] Xorg Upgrade 7.5.2
On Mon, Feb 6, 2012 at 2:45 AM, Martin Wilke m...@freebsd.org wrote: The X11 Team is pleased to announce the next round of Xorg updates. Note that this is experimental so you really have to know what you are doing, read UPDATING in the repository, and follow our exact instructions. We are specifically looking for feedback from Intel, ATI and NVIDIA users. It has been working fine on both 9-RC2 and 10-CURRENT for a couple of days with NVIDIA driver. KWin effects work fine with OpenGL backend. Only two differences noticed: increased memory usage, and some improvements to Synaptics driver. -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla ___ 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: [CFT] Xorg Upgrade 7.5.2
On 02/06/2012 04:43, Daniel Stolpe wrote: Does this mean I can stop using 10.0-current on my Lenovo X121e? ;-) No. :) We need more people running HEAD on their day-to-day systems, not less. Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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][CFT] pkgng beta1 is out
On Mon, Jan 30, 2012 at 01:39:30PM +0100, Baptiste Daroussin wrote:
to use pkgng:
echo WITH_PKGNG=yes /etc/make.conf
make -C /usr/ports/ports-mgmt/pkg install clean
On ia64 9.9-CURRENT:
Script started on Wed Feb 8 10:03:18 2012
make
=== Patching for pkg-1.0.b1
=== Configuring for pkg-1.0.b1
=== FreeBSD 10 autotools fix applied to
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/aclocal.m4
=== FreeBSD 10 autotools fix applied to
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/configure
=== Building for pkg-1.0.b1
=== external (all)
=== external/sqlite (all)
Warning: Object directory not changed from original
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/sqlite
cc -O2 -pipe -fno-strict-aliasing -fPIC -DSQLITE_OMIT_AUTOVACUUM
-DSQLITE_OMIT_BLOB_LITERAL -DSQLITE_OMIT_COMPLETE -DSQLITE_OMIT_DECLTYPE
-DSQLITE_OMIT_DEPRECATED -DSQLITE_OMIT_EXPLAIN -DSQLITE_OMIT_GET_TABLE
-DSQLITE_OMIT_LOAD_EXTENSION -DSQLITE_OMIT_PROGRESS_CALLBACK
-DSQLITE_OMIT_TCL_VARIABLE -DSQLITE_OMIT_UTF16 -DSQLITE_OMIT_CAT
-DSQLITE_OMIT_CHECK -DSQLITE_OMIT_AUTOINIT -DSQLITE_OMIT_COMPILEOPTION_DIAGS
-DSQLITE_OMIT_INTEGRITY_CHECK -DSQLITE_OMIT_BUILTIN_TEST
-DSQLITE_OMIT_SHARED_CACHE -DUSE_PREAD -DSQLITE_THREADSAFE=1
-DSQLITE_TEMP_STORE=3 -DNDEBUG -std=gnu99 -Wsystem-headers -Werror
-Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -Werror -c sqlite3.c
{standard input}: Assembler messages:
{standard input}:115049: Warning: Use of 'mov' may violate WAW dependency 'GR%,
% in 1 - 127' (impliedf), specific resource number is 14
{standard input}:115047: Warning: This is the location of the conflicting usage
building static sqlite3 library
ranlib libsqlite3.a
=== external/libyaml (all)
Warning: Object directory not changed from original
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/api.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/dumper.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/emitter.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/loader.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/parser.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/reader.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/scanner.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/writer.c
building static yaml library
ranlib libyaml.a
=== libpkg (all)
Warning: Object directory not changed from original
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/libpkg
cc -O2 -pipe -fno-strict-aliasing -std=c99
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/libpkg
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/libpkg/../external/sqlite
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/libpkg/../external/libyaml/include
-DPREFIX=\/usr/local\ -g -O0 -std=gnu99
Re: FreeBSD ports which are currently scheduled for deletion
Doug Barton do...@freebsd.org wrote: On 02/08/2012 02:12, per...@pluto.rain.com wrote: lini...@freebsd.org wrote: portname: graphics/vrml2pov description:Convert VRML files to POVRay source maintainer: po...@freebsd.org status: BROKEN deprecated because: unfetchable This seems to be a ports-infrastructure problem, rather than a problem in the vrml2pov port. No, it's a No one cares enough about this port to step forward and maintain it problem. Er, as of a few hours ago (when I tried it), the URL in the distfile link on vrml2pov's download page *exactly* matched the URL that the port tries to fetch. This does not appear to be a case of the distfile having been moved and the port not having caught up: the port is using exactly the same URL to (try to) fetch the distfile as any human would, but it works for the human because browsers understand redirections. The only reason the port doesn't fetch is that the infrastructure doesn't handle that kind of URL properly. Given that, why would it not make more sense to fix the broken ports infrastructure -- thereby also covering any number of other and/or future similar cases -- rather than fixing this one port that is not actually wrong? The infrastructure needs to handle redirections. That's arguable, but once again it's an issue that no one has stepped up to fix. Likely because it would involve grubbing around in bsd.port.mk, which only portmgr@ is allowed to touch :) ___ 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
INDEX now builds successfully on 7.x
___ 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 ports which are currently scheduled for deletion
portname: graphics/vrml2pov description:Convert VRML files to POVRay source maintainer: po...@freebsd.org status: BROKEN deprecated because: unfetchable This seems to be a ports-infrastructure problem, rather than a problem in the vrml2pov port. No, it's a No one cares enough about this port to step forward and maintain it problem. Er, as of a few hours ago (when I tried it), the URL in the distfile link on vrml2pov's download page *exactly* matched the URL that the port tries to fetch. The default FETCH_ARGS include -A which makes fetch fail on redirects; this is presumably because some sites redirect rather than return 404 when a file is not found. In cases when redirect needs to be followed, you need to override FETCH_ARGS in the port's Makefile. See the attached patch (I hope it'll get through the list). I can submit a PR, or some brave committer can apply it right away... Oh, it's actually appears to be fetchable the way it is right now, just remove the BROKEN lines. ___ 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 ports which are currently scheduled for deletion
portname: graphics/vrml2pov
description:Convert VRML files to POVRay source
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: unfetchable
This seems to be a ports-infrastructure problem, rather than a
problem in the vrml2pov port.
No, it's a No one cares enough about this port to step forward
and maintain it problem.
Er, as of a few hours ago (when I tried it), the URL in the distfile
link on vrml2pov's download page *exactly* matched the URL that the
port tries to fetch.
The default FETCH_ARGS include -A which makes fetch fail on redirects;
this is presumably because some sites redirect rather than return 404
when a file is not found. In cases when redirect needs to be followed,
you need to override FETCH_ARGS in the port's Makefile.
See the attached patch (I hope it'll get through the list). I can submit
a PR, or some brave committer can apply it right away...
--- Makefile.orig 2012-02-08 13:18:22.0 +0200
+++ Makefile2012-02-08 13:18:47.0 +0200
@@ -17,13 +17,10 @@
RESTRICTED=Redistribution is not allowed
-BROKEN=unfetchable
-DEPRECATED=${BROKEN}
-EXPIRATION_DATE= 2012-03-21
-
USE_ZIP= yes
USE_GMAKE= yes
MAKEFILE= makefile
+FETCH_ARGS=-Fpr
PLIST_FILES= bin/vrml2pov
NO_WRKSUBDIR= yes
___
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 ports which are currently scheduled for deletion
On Wed, 08 Feb 2012 02:12:39 -0800, perryh wrote: lini...@freebsd.org wrote: portname: graphics/vrml2pov description:Convert VRML files to POVRay source maintainer: po...@freebsd.org status: BROKEN deprecated because: unfetchable This seems to be a ports-infrastructure problem, rather than a problem in the vrml2pov port. make fetch-recursive reports fetch: http://www.chemicalgraphics.com/paul/vrml2pov/dist/v0.7/vrml2pov-src.zip: Moved Temporarily and gives up after the attempt from ftp.FreeBSD.org also fails. However, Firefox successfully downloads the distfile from the chemicalgraphics.com URL. The infrastructure needs to handle redirections. Infrastructure actually explicitly disallows redirects with 'A' flag in FETCH_ARGS. If you can't find the URL where it redirects to, you could specify FETCH_ARGS=-Fpr for such ports. Yuri ___ 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][CFT] pkgng beta1 is out
On Wed, Feb 08, 2012 at 10:08:46AM +, Anton Shterenlikht wrote:
On Mon, Jan 30, 2012 at 01:39:30PM +0100, Baptiste Daroussin wrote:
to use pkgng:
echo WITH_PKGNG=yes /etc/make.conf
make -C /usr/ports/ports-mgmt/pkg install clean
On ia64 9.9-CURRENT:
Script started on Wed Feb 8 10:03:18 2012
make
=== Patching for pkg-1.0.b1
=== Configuring for pkg-1.0.b1
=== FreeBSD 10 autotools fix applied to
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/aclocal.m4
=== FreeBSD 10 autotools fix applied to
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/configure
=== Building for pkg-1.0.b1
=== external (all)
=== external/sqlite (all)
Warning: Object directory not changed from original
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/sqlite
cc -O2 -pipe -fno-strict-aliasing -fPIC -DSQLITE_OMIT_AUTOVACUUM
-DSQLITE_OMIT_BLOB_LITERAL -DSQLITE_OMIT_COMPLETE -DSQLITE_OMIT_DECLTYPE
-DSQLITE_OMIT_DEPRECATED -DSQLITE_OMIT_EXPLAIN -DSQLITE_OMIT_GET_TABLE
-DSQLITE_OMIT_LOAD_EXTENSION -DSQLITE_OMIT_PROGRESS_CALLBACK
-DSQLITE_OMIT_TCL_VARIABLE -DSQLITE_OMIT_UTF16 -DSQLITE_OMIT_CAT
-DSQLITE_OMIT_CHECK -DSQLITE_OMIT_AUTOINIT
-DSQLITE_OMIT_COMPILEOPTION_DIAGS -DSQLITE_OMIT_INTEGRITY_CHECK
-DSQLITE_OMIT_BUILTIN_TEST -DSQLITE_OMIT_SHARED_CACHE -DUSE_PREAD
-DSQLITE_THREADSAFE=1 -DSQLITE_TEMP_STORE=3 -DNDEBUG -std=gnu99
-Wsystem-headers -Werror -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args
-Werror -c sqlite3.c
{standard input}: Assembler messages:
{standard input}:115049: Warning: Use of 'mov' may violate WAW dependency
'GR%, % in 1 - 127' (impliedf), specific resource number is 14
{standard input}:115047: Warning: This is the location of the conflicting
usage
building static sqlite3 library
ranlib libsqlite3.a
=== external/libyaml (all)
Warning: Object directory not changed from original
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/api.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/dumper.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/emitter.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/loader.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/parser.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/reader.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/scanner.c
cc -O2 -pipe -fno-strict-aliasing -fPIC
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/include
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml
-DHAVE_CONFIG_H -std=gnu99 -Wsystem-headers -Werror -Wno-pointer-sign -c
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/external/libyaml/src/writer.c
building static yaml library
ranlib libyaml.a
=== libpkg (all)
Warning: Object directory not changed from original
/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/libpkg
cc -O2 -pipe -fno-strict-aliasing -std=c99
-I/usr/ports/ports-mgmt/pkg/work/pkg-1.0-beta1/libpkg
Re: FreeBSD ports which are currently scheduled for deletion
Doug Barton wrote: On 02/07/2012 17:13, Svyatoslav Lempert wrote: 2012/2/7lini...@freebsd.org: The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: lang/php52 description:PHP Scripting Language maintainer: ad...@lissyara.su deprecated because: PHP 5.2 series is not supported anymore, migrate now expiration date:2012-03-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=langportname=php52 Why so much wish to remove lang/php52? There are numerous security vulnerabilities in it, and so far no one has stepped up to thoroughly address them. If you'd like to volunteer to maintain this version that would be great. Just submit the PR with the following updates: All security patches backported Fix the dependent ports (php52-*) to use the same patches as lang/php52 That's off the top of my head ... there may be other problems. Are you sure there are any known security vulnerabilities not fixed in lang/php52? I think that current maintainer Alex Keda ad...@lissyara.su is doing exelent work with backporting all needed patches to have working and secure PHP 5.2.x in FreeBSD ports tree, so there is no need to remove this port. Migrating from 5.2 to 5.3 or any future version is not possible without modification of PHP scripts. Webhosting servers with old applications must stay with 5.2 until all clients migrate their code to newer version. The last version of PHP 4.4 was released 07-Aug-2008 and is still in ports tree, last version of 5.2 was released 06-Jan-2011 and is well maintained with security patches. I don't see any good reason to remove the port, which have active maintainer fixing all known problems / security vulnerabilities. Miroslav Lachman ___ 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][CFT] pkgng beta1 is out
On Wed, Feb 08, 2012 at 01:21:12PM +0100, Baptiste Daroussin wrote: cc1: warnings being treated as errors usergroup.c: In function 'pkg_add_user_group': usergroup.c:75: warning: implicit declaration of function 'gr_init' usergroup.c:75: warning: nested extern declaration of 'gr_init' usergroup.c:76: warning: implicit declaration of function 'gr_lock' usergroup.c:76: warning: nested extern declaration of 'gr_lock' usergroup.c:77: warning: implicit declaration of function 'gr_fini' usergroup.c:77: warning: nested extern declaration of 'gr_fini' usergroup.c:80: warning: implicit declaration of function 'gr_tmp' usergroup.c:80: warning: nested extern declaration of 'gr_tmp' usergroup.c:84: warning: implicit declaration of function 'gr_copy' usergroup.c:84: warning: nested extern declaration of 'gr_copy' usergroup.c:88: warning: implicit declaration of function 'gr_mkdb' usergroup.c:88: warning: nested extern declaration of 'gr_mkdb' *** Error code 1 Your current is too old, could you please try to update it? the gr_* function where committed in r228545 version. Thanks, I got it working on r231193. I applied the portmaster patch from git, then running portmaster -a, I get: === Port directory: /usr/ports/devel/xorg-macros === Starting check for build dependencies === Gathering dependency list for devel/xorg-macros from ports === Launching child to install ports-mgmt/pkg xorg-macros-1.15.0 ports-mgmt/pkg which ends in === Installing for pkg-1.0.b1 === Generating temporary packing list === Checking if ports-mgmt/pkg already installed === pkg-1.0.b1 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of ports-mgmt/pkg without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/ports-mgmt/pkg. What am I doing wrong? Many thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: FreeBSD ports which are currently scheduled for deletion
2012/2/8 Miroslav Lachman 000.f...@quip.cz: Doug Barton wrote: On 02/07/2012 17:13, Svyatoslav Lempert wrote: 2012/2/7lini...@freebsd.org: The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: lang/php52 description: PHP Scripting Language maintainer: ad...@lissyara.su deprecated because: PHP 5.2 series is not supported anymore, migrate now expiration date: 2012-03-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=langportname=php52 Why so much wish to remove lang/php52? There are numerous security vulnerabilities in it, and so far no one has stepped up to thoroughly address them. If you'd like to volunteer to maintain this version that would be great. Just submit the PR with the following updates: All security patches backported Fix the dependent ports (php52-*) to use the same patches as lang/php52 That's off the top of my head ... there may be other problems. Are you sure there are any known security vulnerabilities not fixed in lang/php52? I think that current maintainer Alex Keda ad...@lissyara.su is doing exelent work with backporting all needed patches to have working and secure PHP 5.2.x in FreeBSD ports tree, so there is no need to remove this port. Migrating from 5.2 to 5.3 or any future version is not possible without modification of PHP scripts. Webhosting servers with old applications must stay with 5.2 until all clients migrate their code to newer version. The last version of PHP 4.4 was released 07-Aug-2008 and is still in ports tree, last version of 5.2 was released 06-Jan-2011 and is well maintained with security patches. I don't see any good reason to remove the port, which have active maintainer fixing all known problems / security vulnerabilities. Miroslav Lachman Please look to PR http://www.freebsd.org/cgi/query-pr.cgi?pr=164849 -- Svyatoslav ___ 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: helping out INDEX builds. best practices?
On Tue, Feb 07, 2012 at 09:07:03PM -0500, Michael Scheidell wrote: ok, but if I open a pr for subversion16, I am going to need to hack GNATS and add a 'blocks' or 'depends on' so I get notified when its committed :-) for the blocked PR: state=suspended and give a reason why. for the blocking PR: X-GNATS-Notify=your-email-address mcl ___ 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: net/freerdp 1.0.0
on 08/02/2012 03:20 Doug Barton said the following: On 02/07/2012 02:49, Andriy Gapon wrote: I would like to ask you to review and test the port in this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=164843 Using the latest shar on up to date 8-stable i386 it seems to run fine. FWIW I'm using the port with all of the OPTIONS UNchecked. A couple of notes: * There is a man page listed in the Makefile, but it doesn't seem to exist. Weird. It definitely exists in the source code and here it even gets installed: $ pkg_info -W /usr/local/man/man1/xfreerdp.1.gz /usr/local/man/man1/xfreerdp.1.gz was installed by package freerdp-1.0.0 BTW, the content of this manual seems to be a bit outdated. There used to be a better manual page online at this location: http://www.freerdp.com/wiki/doku.php?id=documentation:userdocs:xfreerdp_manpage but now it seems to be gone. But google cache has it for time being: http://webcache.googleusercontent.com/search?q=cache:Mgy8LqzGuZEJ:www.freerdp.com/wiki/doku.php%3Fid%3Ddocumentation:userdocs:xfreerdp_manpage+cd=2hl=enct=clnklr=lang_en|lang_ukclient=firefox-a * When I exit I get this: Failed to check xfreerdp file descriptor I've seen this message too. Maybe it's something worth reporting upstream. I also would to discuss with the port's users the best approach to updating it. Given that I use this daily for $WORK and am heavily dependent on it, I really appreciate you asking this question. :) My suggestion is that once you're confident that it is effective as a superset of the old version then go ahead and update the port. If it turns out that people have trouble with the new version that cannot be addressed in a timely manner you can always proceed with adding the -legacy port that you mentioned in your PR. It seems that this version works fine for, but I am not sure about the complete compatibility. Actually, I seem to experience some problem with embedding freerdp window inside another application using -X option. I wonder if anyone else uses that option and can report how it works. One word of caution for those (like me) who have a button or other mechanism to start it from your DE, and are connecting to something that's SSL protected. Start it on the command line first, so that you can answer the dialog about accepting the SSL certificate. I filled a 2G /var/log in less than a minute before I realized why the thing hadn't popped up a window yet. Good advice. I also had to use --no-nla option to get freerdp working the way it did before. BTW, just in case, just noticed this page referenced from the freerdp's main page: http://remmina.sourceforge.net/ Looks like a potentially useful software. -- Andriy Gapon ___ 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: [CFT] Xorg Upgrade 7.5.2
Hello all, I am testing the all.13.1.patch , as well as xorg 7.5.2 on FreeBSD HEAD I have a Asus n53sv laptop with a sandybridge i7 CPU (as well as a Nvidia 540m) my main problem is I can't start x becasue I get these errors [ 301.537] (EE) No devices detected. [ 301.537] Fatal server error: [ 301.537] no screens found [ 301.537] if anyone could provide me suggestions. that would be great :) This is a clean install with no ports installed before I built the xorg-dev svn I will provide as much detail as possible below: cat /etc/make.conf WITH_NEW_XORG=yes WITH_KMS=yes # added by use.perl 2012-02-08 10:03:27 PERL_VERSION=5.12.4 301.354] (**) ModulePath set to /usr/local/lib/xorg/modules [ 301.354] (**) Extension Composite is enabled [ 301.354] (II) Loader magic: 0x7c7c60 [ 301.354] (II) Module ABI versions: [ 301.354] X.Org ANSI C Emulation: 0.4 [ 301.354] X.Org Video Driver: 10.0 [ 301.354] X.Org XInput driver : 12.2 [ 301.354] X.Org Server Extension : 5.0 [ 301.355] (!!) More than one possible primary device found [ 301.355] (--) PCI: (0:0:2:0) 8086:0116:1043:1642 rev 9, Mem @ 0xdc40/4194304, 0xb000/268435456, I/O @ 0xe000/64, BIOS @ 0x/65536 [ 301.355] (--) PCI: (0:1:0:0) 10de:0df4:1043:1642 rev 161, Mem @ 0xdb00/16777216, 0xc000/268435456, 0xd000/33554432, I/O @ 0xd000/128, BIOS @ 0x/65536 [ 301.355] (II) extmod will be loaded. This was enabled by default and also specified in the config file. [ 301.355] (II) dbe will be loaded. This was enabled by default and also specified in the config file. [ 301.355] (II) glx will be loaded. This was enabled by default and also specified in the config file. [ 301.355] (II) record will be loaded by default. [ 301.355] (II) dri will be loaded by default. [ 301.355] (II) dri2 will be loaded by default. [ 301.355] (II) LoadModule: ddc [ 301.355] (II) Module ddc already built-in [ 301.355] (II) LoadModule: dbe [ 301.388] (II) Loading /usr/local/lib/xorg/modules/extensions/libdbe.so [ 301.400] (II) Module dbe: vendor=X.Org Foundation [ 301.400] compiled for 1.10.4, module version = 1.0.0 [ 301.400] Module class: X.Org Server Extension [ 301.400] ABI class: X.Org Server Extension, version 5.0 [ 301.400] (II) Loading extension DOUBLE-BUFFER [ 301.400] (II) LoadModule: extmod [ 301.401] (II) Loading /usr/local/lib/xorg/modules/extensions/libextmod.so [ 301.408] (II) Module extmod: vendor=X.Org Foundation [ 301.408] compiled for 1.10.4, module version = 1.0.0 [ 301.408] Module class: X.Org Server Extension [ 301.408] ABI class: X.Org Server Extension, version 5.0 [ 301.408] (II) Loading extension MIT-SCREEN-SAVER [ 301.408] (II) Loading extension XFree86-VidModeExtension [ 301.408] (II) Loading extension XFree86-DGA [ 301.408] (II) Loading extension DPMS [ 301.408] (II) Loading extension XVideo [ 301.408] (II) Loading extension XVideo-MotionCompensation [ 301.408] (II) Loading extension X-Resource [ 301.408] (II) LoadModule: glx [ 301.409] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so [ 301.418] (II) Module glx: vendor=X.Org Foundation [ 301.418] compiled for 1.10.4, module version = 1.0.0 [ 301.418] ABI class: X.Org Server Extension, version 5.0 [ 301.419] (==) AIGLX disabled [ 301.419] (II) Loading extension GLX [ 301.420] (II) LoadModule: record [ 301.420] (II) Loading /usr/local/lib/xorg/modules/extensions/librecord.so [ 301.421] (II) Module record: vendor=X.Org Foundation [ 301.421] compiled for 1.10.4, module version = 1.13.0 [ 301.421] Module class: X.Org Server Extension [ 301.421] ABI class: X.Org Server Extension, version 5.0 [ 301.421] (II) Loading extension RECORD [ 301.421] (II) LoadModule: dri [ 301.422] (II) Loading /usr/local/lib/xorg/modules/extensions/libdri.so [ 301.437] (II) Module dri: vendor=X.Org Foundation [ 301.437] compiled for 1.10.4, module version = 1.0.0 [ 301.437] ABI class: X.Org Server Extension, version 5.0 [ 301.437] (II) Loading extension XFree86-DRI [ 301.437] (II) LoadModule: dri2 [ 301.438] (II) Loading /usr/local/lib/xorg/modules/extensions/libdri2.so [ 301.438] (II) Module dri2: vendor=X.Org Foundation [ 301.438] compiled for 1.10.4, module version = 1.2.0 [ 301.438] ABI class: X.Org Server Extension, version 5.0 [ 301.438] (II) Loading extension DRI2 [ 301.438] (II) LoadModule: intel [ 301.465] (II) Loading /usr/local/lib/xorg/modules/drivers/intel_drv.so [ 301.502] (II) Module intel: vendor=X.Org Foundation [ 301.502] compiled for 1.10.4, module version = 2.17.0 [ 301.502] Module class: X.Org Video Driver [ 301.502] ABI class: X.Org Video Driver, version 10.0 [ 301.502] (II) LoadModule: mouse [ 301.503] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so [ 301.516] (II) Module mouse: vendor=X.Org Foundation [ 301.516] compiled for 1.10.4, module version = 1.7.1 [ 301.516] Module class: X.Org XInput
Re: [HEADSUP][CFT] pkgng beta1 is out
On Wednesday 08 February 2012 16:07:16 Anton Shterenlikht wrote: I applied the portmaster patch from git, then running portmaster -a, I get: How did you apply the patch? -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla The Marines: The few, the proud, the not very bright. signature.asc Description: This is a digitally signed message part.
porting percona's xtrabackup (currently version 1.6.4)
Hi guys,
The last version of percona's xtrabackup utility in the ports is 1.1. I
think this is a bit old. Therefore, I have written an e-mail to the
maintainer of the port asking if it would be possible to create a newer
version. No answer yet.
Since I'm the curious type of guy, I went ahead and tried it out myself. So
far, I have this:
PORTNAME= xtrabackup
PORTVERSION= 1.6.4
CATEGORIES= databases
MASTER_SITES=
http://www.percona.com/downloads/XtraBackup/XtraBackup-1.6.4/source/
COMMENT= OpenSource version of InnoDB backup with support of Percona
extensions
MAKE_JOBS_SAFE= yes
USE_GMAKE= yes
OPTIONS= innodb51_builtin built-in InnoDB in MySQL 5.1 off \
innodb51 InnoDB plugin in MySQL 5.1 off \
innodb55 InnoDB in MySQL 5.5 on \
xtradb51 Percona Server with XtraDB 5.1 off \
xtradb55 Percona Server with XtraDB 5.5 off
BUILD_DEPENDS= bash:${PORTSDIR}/shells/bash
bzr:${PORTSDIR}/devel/bazaar-ng
.include bsd.port.options.mk
.if defined(WITH_innodb51_builtin)
.endif
.if defined(WITH_innodb55)
.endif
.if defined(WITH_xtradb51)
.endif
.if defined(WITH_xtradb55)
.endif
.include bsd.port.mk
Problems so far:
The xtrabackup archive has no [configure script. Instead, there is 1
script, build.sh that takes care of everything (using bash). Installation
rolls down to:
AUTO_DOWNLOAD=YES ./utils/build.sh engine_option --- this is where
the dialog box should kick in
My question is:
1) Is there a way to connect this script to the make (I think) command of
the ports framework and to the OPTIONS parameter from the port?
--
Best regards,
Claudiu Vasadi
___
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: porting percona's xtrabackup (currently version 1.6.4)
Hi claudiu,
flo@ and pgollucci@ (myself) should be able to help as maintainers of
percona-toolkit and percona.
Let me get back to you tonight or Friday.
You might look at CONFIGURE_SCRIPT= in the mean-time. See Mk/bsd.port.mk.
On 02/08/12 21:36, claudiu vasadi wrote:
Hi guys,
The last version of percona's xtrabackup utility in the ports is 1.1. I
think this is a bit old. Therefore, I have written an e-mail to the
maintainer of the port asking if it would be possible to create a newer
version. No answer yet.
Since I'm the curious type of guy, I went ahead and tried it out myself. So
far, I have this:
PORTNAME= xtrabackup
PORTVERSION= 1.6.4
CATEGORIES= databases
MASTER_SITES=
http://www.percona.com/downloads/XtraBackup/XtraBackup-1.6.4/source/
COMMENT= OpenSource version of InnoDB backup with support of Percona
extensions
MAKE_JOBS_SAFE= yes
USE_GMAKE= yes
OPTIONS= innodb51_builtin built-in InnoDB in MySQL 5.1 off \
innodb51 InnoDB plugin in MySQL 5.1 off \
innodb55 InnoDB in MySQL 5.5 on \
xtradb51 Percona Server with XtraDB 5.1 off \
xtradb55 Percona Server with XtraDB 5.5 off
BUILD_DEPENDS= bash:${PORTSDIR}/shells/bash
bzr:${PORTSDIR}/devel/bazaar-ng
.include bsd.port.options.mk
.if defined(WITH_innodb51_builtin)
.endif
.if defined(WITH_innodb55)
.endif
.if defined(WITH_xtradb51)
.endif
.if defined(WITH_xtradb55)
.endif
.include bsd.port.mk
Problems so far:
The xtrabackup archive has no [configure script. Instead, there is 1
script, build.sh that takes care of everything (using bash). Installation
rolls down to:
AUTO_DOWNLOAD=YES ./utils/build.sh engine_option --- this is where
the dialog box should kick in
My question is:
1) Is there a way to connect this script to the make (I think) command of
the ports framework and to the OPTIONS parameter from the port?
--
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354
Member, Apache Software Foundation
Committer,FreeBSD Foundation
Consultant, P6M7G8 Inc.
Director Operations, Ridecharge Inc.
Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.
signature.asc
Description: OpenPGP digital signature
Re: net/freerdp 1.0.0
On Tue, 07 Feb 2012 04:49:39 -0600, Andriy Gapon a...@freebsd.org wrote: I would like to ask you to review and test the port in this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=164843 I also would to discuss with the port's users the best approach to updating it. Thank you. Doesn't compile. [ 21%] Building C object libfreerdp-kbd/CMakeFiles/freerdp-kbd.dir/layouts_xkb.c.o /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:25:22: error: X11/Xlib.h: No such file or directory /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:26:24: error: X11/XKBlib.h: No such file or directory /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:27:36: error: X11/extensions/XKBfile.h: No such file or directory /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:28:37: error: X11/extensions/XKBrules.h: No such file or directory /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c: In function 'init_xkb': /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:45: warning: implicit declaration of function 'XkbQueryExtension' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c: In function 'detect_keyboard_layout_from_xkb': /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:74: error: 'XkbRF_VarDefsRec' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:74: error: (Each undeclared identifier is reported only once /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:74: error: for each function it appears in.) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:74: error: expected ';' before 'rules_names' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:75: error: 'XKeyboardState' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:75: error: expected ';' before 'coreKbdState' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:76: error: 'XkbStateRec' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:76: error: expected ';' before 'state' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:80: warning: implicit declaration of function 'XkbRF_GetNamesProp' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:80: error: 'rules_names' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:85: warning: implicit declaration of function 'XGetKeyboardControl' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:85: error: 'coreKbdState' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:87: warning: implicit declaration of function 'XkbGetState' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:87: error: 'XkbUseCoreKbd' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:87: error: 'state' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:87: error: 'Success' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c: In function 'init_keycodes_from_xkb': /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:112: error: 'XkbDescPtr' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:112: error: expected ';' before 'xkb' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:114: error: 'xkb' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:114: warning: implicit declaration of function 'XkbGetMap' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:114: error: 'XkbUseCoreKbd' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:116: warning: implicit declaration of function 'XkbGetNames' /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:116: error: 'XkbKeyNamesMask' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:116: error: 'Success' undeclared (first use in this function) /usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:156: warning:
Re: porting percona's xtrabackup (currently version 1.6.4)
Hi Phillip,
I played around a bit and and had some progress. This is what I have now:
PORTNAME= xtrabackup
PORTVERSION= 1.6.4
CATEGORIES= databases
MASTER_SITES=
http://www.percona.com/downloads/XtraBackup/XtraBackup-1.6.4/source/
MAINTAINER= claudiu.vas...@gmail.com
COMMENT= OpenSource version of InnoDB backup with support of Percona
extensions
MAKE_JOBS_SAFE= yes
OPTIONS= innodb51_builtin built-in InnoDB in MySQL 5.1 off \
innodb51 InnoDB plugin in MySQL 5.1 off \
innodb55 InnoDB in MySQL 5.5 on \
xtradb51 Percona Server with XtraDB 5.1 off \
xtradb55 Percona Server with XtraDB 5.5 off
BUILD_DEPENDS= bash:${PORTSDIR}/shells/bash \
bzr:${PORTSDIR}/devel/bazaar-ng \
wget:${PORTSDIR}/ftp/wget
HAS_CONFIGURE= yes
CONFIGURE_ENV= AUTO_DOWNLOAD=yes
CONFIGURE_WRKSRC= ${WRKSRC}
CONFIGURE_SCRIPT= utils/build.sh
# not really working, allway picking up innodb51_builtin (first option)
instead of the option selected
CONFIGURE_ARGS= ${OPTIONS}
.include bsd.port.mk
For the moment, this is my TO-DO list:
1) make $OPTIONS be delivered to the build.sh script (I tried via the
CONFIGURE_ARGS but I guess that's not the way to do it. I also read
bsd.port.mk but couldn;t see how I could accomplish this)
2) make the build.sh script run under a bash shell
3) pkg-plist
4) definitely more but I'm tired now
Any pointers are greatly appreciated.
--
Best regards,
Claudiu Vasadi
___
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?
On 02/08/2012 07:36, Alex Dupre wrote:
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?
Looking again at this bit of bpm:
PLIST_SUB+= DOCSDIR=${DOCSDIR_REL} \
EXAMPLESDIR=${EXAMPLESDIR_REL} \
DATADIR=${DATADIR_REL} \
WWWDIR=${WWWDIR_REL} \
ETCDIR=${ETCDIR_REL}
You're right, the silliness is universal. I was focused on WWWDIR
because I was working with it. They should probably all go away, but I
don't have the time atm to do an exhaustive search on where/how they are
all used.
Doug
--
It's always a long day; 86400 doesn't fit into a short.
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
___
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][CFT] pkgng beta1 is out
On Wed, 8 Feb 2012 15:07:16 +, Anton Shterenlikht wrote: On Wed, Feb 08, 2012 at 01:21:12PM +0100, Baptiste Daroussin wrote: cc1: warnings being treated as errors usergroup.c: In function 'pkg_add_user_group': usergroup.c:75: warning: implicit declaration of function 'gr_init' usergroup.c:75: warning: nested extern declaration of 'gr_init' usergroup.c:76: warning: implicit declaration of function 'gr_lock' usergroup.c:76: warning: nested extern declaration of 'gr_lock' usergroup.c:77: warning: implicit declaration of function 'gr_fini' usergroup.c:77: warning: nested extern declaration of 'gr_fini' usergroup.c:80: warning: implicit declaration of function 'gr_tmp' usergroup.c:80: warning: nested extern declaration of 'gr_tmp' usergroup.c:84: warning: implicit declaration of function 'gr_copy' usergroup.c:84: warning: nested extern declaration of 'gr_copy' usergroup.c:88: warning: implicit declaration of function 'gr_mkdb' usergroup.c:88: warning: nested extern declaration of 'gr_mkdb' *** Error code 1 Your current is too old, could you please try to update it? the gr_* function where committed in r228545 version. Thanks, I got it working on r231193. I applied the portmaster patch from git, then running portmaster -a, I get: === Port directory: /usr/ports/devel/xorg-macros === Starting check for build dependencies === Gathering dependency list for devel/xorg-macros from ports === Launching child to install ports-mgmt/pkg xorg-macros-1.15.0 ports-mgmt/pkg which ends in === Installing for pkg-1.0.b1 ===Generating temporary packing list === Checking if ports-mgmt/pkg already installed ===pkg-1.0.b1 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of ports-mgmt/pkg without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/ports-mgmt/pkg. What am I doing wrong? You are likely missing use_pkgng=yes in your portmaster.rc. Yuri ___ 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?
On 02/08/12 23:24, Doug Barton wrote:
On 02/08/2012 07:36, Alex Dupre wrote:
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?
Looking again at this bit of bpm:
PLIST_SUB+= DOCSDIR=${DOCSDIR_REL} \
EXAMPLESDIR=${EXAMPLESDIR_REL} \
DATADIR=${DATADIR_REL} \
WWWDIR=${WWWDIR_REL} \
ETCDIR=${ETCDIR_REL}
You're right, the silliness is universal. I was focused on WWWDIR
because I was working with it. They should probably all go away, but I
don't have the time atm to do an exhaustive search on where/how they are
all used.
Doug
Ah, the lightbulb goes off.
pkg-plist is supposed to be relative to @cwd which may or may not be
${LOCALBASE} or ${PREFIX} hence abs paths should be avoided.
That said, I think dougb's original patch
+ WWWDIR=${WWWDIR:S,^${PREFIX}/,,}
accomplishes this quite nicely and removes 1-3 variables in the process.
--
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354
Member, Apache Software Foundation
Committer,FreeBSD Foundation
Consultant, P6M7G8 Inc.
Director Operations, Ridecharge Inc.
Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.
signature.asc
Description: OpenPGP digital signature
Re: What use is WWWDIR_REL?
On Tue, Feb 7, 2012 at 9:28 PM, Doug Barton do...@freebsd.org wrote:
Following up to my previous post about Why isn't WWWDIR_REL in the
default PLIST_SUB I broke open bsd.port.mk and found this:
PLIST_SUB+= DOCSDIR=${DOCSDIR_REL} \
EXAMPLESDIR=${EXAMPLESDIR_REL} \
DATADIR=${DATADIR_REL} \
WWWDIR=${WWWDIR_REL} \ ***!!!
ETCDIR=${ETCDIR_REL}
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 searched the
ports tree and found 1,063 uses of it (outside of bpm itself). 1,035 of
them are literals in a pkg-plist, which at this point looks completely
useless. Of the 28 others 13 of them are PLIST_SUB related, which
apparently can also be removed. Most of the other 15 look like mistakes,
and all of them look like they can be fixed with little difficulty.
Those 1035 ports that are using WWWDIR_REL in their pkg-plist are
wrong and should be changed to use WWWDIR. Since PLIST_SUB will
automatically replace %%WWWDIR%% with ${WWWDIR_REL} in the pkg-plist.
So I'd like to propose the attached, not to be included until the
existing uses of WWWDIR_REL are updated of course. Can anyone tell me
why this would be a bad idea? I think being able to just use %%WWWDIR%%
in the plist would be a lot less confusing.
I believe the original purpose of the *_REL variables in bsd.port.mk
was to make maintaining bsd.port.mk easier.
These variables were introduced in bsd.port.mk version 1.557.
http://www.freebsd.org/cgi/query-pr.cgi?pr=110781 - adds the *_REL
variables to bsd.port.mk
http://www.freebsd.org/cgi/query-pr.cgi?pr=105529 - adds WWWDIR to bsd.port.mk
Portlint most likely should be updated to do the following:
- look for the use of these *_REL variables in the pkg-plist and flag
them as an error, and suggest to use the non *_REL variable instead.
- Check the ports Makefile for the use of the *_REL variables in
PLIST_SUB and flag those uses as an error.
Scot
___
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
OO 3.3.0 fails to build connectivity module on amd64 9-STABLE
Hi,
The OO 3.3.0 build fails in the connectivity module with the following
error:
Compiling: connectivity/source/parse/wrap_sqlbison.cxx
c++ -fmessage-length=0 -c -O2 -fno-strict-aliasing -DENABLE_LAYOUT=0
-DENABLE_LAYOUT_EXPERIMENTAL=0 -fvisibility=hidden -I.
-I../../unxfbsdx.pro/misc -I../../unxfbsdx.pro/inc/sql -I../inc -I../../inc/pch
-I../../inc -I../../unx/inc -I../../unxfbsdx.pro/inc -I.
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solver/330/unxfbsdx.pro/inc/stl
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solver/330/unxfbsdx.pro/inc/external
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solver/330/unxfbsdx.pro/inc
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solenv/unxfbsdx/inc
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solenv/inc
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/res
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solver/330/unxfbsdx.pro/inc/stl
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solenv/inc/Xp31
-I/usr/local/diablo-jdk1.6.0/include
-I/usr/local/diablo-jdk1.6.0/include/freebsd -I/usr/local/diablo-jdk1.6.0/i
nclude/bs
d -I/usr/local/diablo-jdk1.6.0/include/linux
-I/usr/local/diablo-jdk1.6.0/include/native_threads/include
-I/usr/local/include
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solver/330/unxfbsdx.pro/inc/offuh
-I. -I../../res -I. -pipe -fvisibility-inlines-hidden -g1 -Wall -Wextra
-Wendif-labels -Wshadow -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor
-fpic -DFREEBSD -DUNX -DVCL -DGCC -DC341 -DX86_64 -D_PTHREADS -D_REENTRANT
-DNEW_SOLAR -D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400
-DHAVE_GCC_VISIBILITY_FEATURE -DX86_64 -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/include/c++/4.2 -DSUPD=330 -DPRODUCT -DNDEBUG
-DOSL_DEBUG_LEVEL=0 -DOPTIMIZE -DCUI -DSOLAR_JAVA
-DOOO_DLLIMPLEMENTATION_DBTOOLS -DSHAREDLIB -D_DLL_ -fexceptions
-fno-enforce-eh-specs -DEXCEPTIONS_ON -o
../../unxfbsdx.pro/slo/wrap_sqlbison.o
/usr/ports/editors/openoffice.org-3/work/OOO330_m20/connectivity/source/parse/wrap_sqlbison.cxx
In file included from
/usr/ports/editors/openoffice.org-3/work/OOO330_m20/connectivity/source/parse/wrap_sqlbison.cxx:31:
../../unxfbsdx.pro/misc/sqlbison.cxx: In function 'int SQLyyparse()':
../../unxfbsdx.pro/misc/sqlbison.cxx:7813: error: invalid conversion from
'const char*' to 'sal_Char*'
../../unxfbsdx.pro/misc/sqlbison.cxx:7813: error: initializing argument 1 of
'void connectivity::OSQLParser::error(sal_Char*)'
dmake: Error code 1, while making '../../unxfbsdx.pro/slo/wrap_sqlbison.obj'
Ports tree was csuped yesterday and all installed ports are up to date.
System info that might be useful...
lstewart@lstewart uname -a
FreeBSD lstewart 9.0-STABLE FreeBSD 9.0-STABLE #1 r231173M: Wed Feb 8
16:14:51 EST 2012 lstewart@lstewart:/usr/obj/usr/src/sys/DESKTOP amd64
lstewart@lstewart pkg_info -x bison
Information for bison-2.5,1:
Relevant lines from /etc/make.conf:
.if ${.CURDIR:M*/editors/openoffice.org-3}
WITH_KDE4=1
LOCALIZED_LANG=en-GB
.endif
I'm running KDE 4.7.4.
Any thoughts on how to fix?
Cheers,
Lawrence
___
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
