Re: [CFT] Xorg 7.7 ready for testing!

2012-06-10 Thread Ivan Klymenko
В Thu, 7 Jun 2012 20:37:53 +0800
Martin Wilke m...@freebsd.org пишет:

 Hi Fans,
 
 The FreeBSD Xorg Team is pleased to announce Xorg 7.7 Release. We are
 very happy to be able to Call for testing shortly after the Xorg team
 annouced 7.7 release. This CFT is also open for discussion on how we
 should move forward with xorg release as we are facing some issues and
 we would like to ask for your opinion. Right now we have 2 existing
 xorg versions in our Ports Tree. The situation is quite bad due to our
 poor graphic card support. That means we do not have much choice but
 to take it as how it is now. But with regards to mesa support, we
 have to face some new challanges.
 
 With the new mesa 8.0 release, accelerated support for a number of
 older graphic cards was dropped. At the moment we are not sure how to
 deal with that.We are thinking of just replacing mesa 7.11 with 8.0 or
 making a new flag like WITH_MESA= 7.11.2 / 8.0 in combination with
 WITH_NEW_XORG, and let the mesa 7.6.1 set as default together with the
 old xorg version. Obviosly the latter option make the already complex
 situation more complex. The problem is, users, especially  the new
 ones can easily get confused with it. Another issue is, the
 packages.We can't deliver a package set with the new Xorg releases.
 This means users with new hardware will have to compile everything by
 themselves. Though I'm totally fine with compiling, not everyone has
 the CPU power to compile everything. What I'm trying to say is, I
 would love to see the newer xorg released as the default version, but
 i know this will break a lot of old hardware. The thing is, when we
 want to try to become a Modern Operating System, I dont see any other
 way to make the new xorg as default but to give Users the chance to
 compile the old xorg with a flag like WITH_OLD_XORG.
 
 Some notes regarding KMS support:
 KMS Support has been completely migrated to FreeBSD 10. The MFC to 9
 will come soon, that means so long its not MFC'd to 9-Stable, users
 need to get the latest patch from our x11 mailing list.
 
 This testing includes
 * libdrm 2.4.34 (including KMS support)
 * mesa 8.0.3
 * full Xorg 7.7 release Change log
   http://www.x.org/releases/X11R7.7/changelog.html
 
 Checkout Xorg Development Repo:
 You will need to install devel/subversion in order to checkout the
 xorg repo. Next, you will need to add WITH_NEW_XORG=yes in
 your /etc/make.conf if you want to try out the new Xorg and mesa. Note
 that if you are not qualified for the KMS patch, you shouldn’t use
 WITH_NEW_XORG=yes because the old intel driver doesn’t build with the
 new X server. If you are qualified, you should also set WITH_KMS=yes
 in /etc/make.conf. Nvidia and ATI users should set WITH_NEW_XORG=yes.
 
 svn co https://trillian.chruetertee.ch/svn/ports/trunk
 
 A small merge script to merge the svn checkout into the real portstree
 can be found here:
 
 http://people.freebsd.org/~miwi/xorg/xorgmerge
 
 The script is a modified version of the old kdemerge script. Please
 set the KDEDIR variable to the path of your X.org ports. After
 merging, run one of the following command, depending on which tool
 you use to manage your installed packages.
 
 portupgrade -af \*
 portmaster -a
 
 
 After installing these, you will have to rebuild all xf86-* ports. We
 will bump all releated ports during the commit to the ports tree.
 
 Roadmap:
 Our current plan is to let the CFT running for a while, and see what
 the outcome of the discussion above is. We hope to get a lot of
 feedback to solve as many problems as possible. Also we are working on
 the libglut to freeglut migration, this will definitely complete
 before we import Xorg 7.7. So we still have enough time.  We are
 looking forward for your feedback.
 
 - miwi on behalf of the FreeBSD X11 Team
 
 PS: Please reply only to x11@ thanks.
 

uname -a
FreeBSD nonamehost 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r236313: Fri Jun  1 
20:20:31 EEST 2012 ivan@nonamehost:/usr/obj/usr/src/sys/mk10  amd64

tree port updated three days ago
port x11-servers/xorg-server build error

gmake[4]: Выход из каталога 
`/usr/ports_build/usr/ports/x11-servers/xorg-server/work/xorg-server-1.12.2/hw/xfree86/man'
gmake[4]: Вход в каталог 
`/usr/ports_build/usr/ports/x11-servers/xorg-server/work/xorg-server-1.12.2/hw/xfree86'
CPP='cpp' AWK='gawk' /bin/sh ./sdksyms.sh ../.. -O2 -ftree-vectorize 
-mfpmath=sse -mssse3 -pipe -march=core2 -fno-strict-aliasing 
-DHAVE_DIX_CONFIG_H -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 
-Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast 
-Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized 
-Wshadow -Wcast-qual -Wmissing-noreturn -Wmissing-format-attribute 
-Wredundant-decls -Werror=implicit -Werror=nonnull -Werror=init-self 
-Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type 
-Werror=trigraphs -Werror=write-strings -Werror=address 

Re: [HEADSUP] Please convert your ports to new options framework

2012-06-10 Thread Thomas Mueller
from Doug Barton do...@freebsd.org:

There's a What users need to know section here:

http://wiki.freebsd.org/Ports/Options/OptionsNG

Regards,
Bryan Drewery

That looks helpful,  Thanks!

There are also many other useful FreeBSD-pertinent guides on wiki.freebsd.org .

Tom
___
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: ports/textproc/stardict3

2012-06-10 Thread Matthias Apitz
El día Tuesday, November 22, 2011 a las 05:37:03PM +, Max Brazhnikov 
escribió:

 On Fri, 18 Nov 2011 13:54:04 +0100, Matthias Apitz wrote:
  Hello,
  
  The port (ports tree from CVS) ports/textproc/stardict3
  
  ports/textproc/stardict3
  PORTVERSION=3.0.3
  MAINTAINER= m...@freebsd.org
  
  installs fine on 10-CURRENT, but the application just crahes or runs
  into a CPU loop; if it runs into CPU loop there is a core file of 'troff',
  i.e. it seems that it started for some man page reason the troff(1) and
  after this it loops;
 Stardict has plugin for displaying man pages.
  
  ...
  I could go back to 3.0.3 and provide more details of the crash, but I
  can't debug or solve this on my own. Or should I file a bug report?
 
 backtrace would be nice to have.

Hi Max,

I've installed another fresh 10-CURRENT (r235646, ports from CVS as of
May 19) and luckily it crashes again reproduceable; a bt of gdb looks
like this:

$ gdb /usr/local/bin/stardict stardict.core
...
#0  0x2966868b in thr_kill () from /lib/libc.so.7
[New Thread 29c07e00 (LWP 100375/stardict)]
[New Thread 29c03300 (LWP 100369/stardict)]
[New Thread 29c03080 (LWP 100203/stardict)]
(gdb) bt
#0  0x2966868b in thr_kill () from /lib/libc.so.7
#1  0x295ffed6 in pthread_sigmask () from /lib/libthr.so.3
#2  0x296005ab in raise () from /lib/libthr.so.3
#3  0x2971ddea in abort () from /lib/libc.so.7
#4  0x291bb6ec in g_assertion_message () from
/usr/local/lib/libglib-2.0.so.0
#5  0x291bbd4d in g_assertion_message_expr ()
   from /usr/local/lib/libglib-2.0.so.0
#6  0x08118a6b in HttpClient::on_connected ()
#7  0x0805a232 in ?? ()
#8  0x0805e63a in ?? ()
#9  0x080b8e69 in std::operator+char, std::char_traitschar,
std::allocatorchar  ()
#10 0x080b8eab in std::operator+char, std::char_traitschar,
std::allocatorchar  ()
#11 0x28965591 in gtk_marshal_BOOLEAN__VOID ()
   from /usr/local/lib/libgtk-x11-2.0.so.0
#12 0x2911bea3 in g_closure_invoke () from
/usr/local/lib/libgobject-2.0.so.0
#13 0x29133992 in g_signal_handlers_block_matched ()
   from /usr/local/lib/libgobject-2.0.so.0
#14 0x291359f0 in g_signal_emit_valist ()
   from /usr/local/lib/libgobject-2.0.so.0
#15 0x29135c70 in g_signal_emit_by_name ()
   from /usr/local/lib/libgobject-2.0.so.0
#16 0x289ce2f2 in gtk_target_list_unref ()
   from /usr/local/lib/libgtk-x11-2.0.so.0
#17 0x289ce6a5 in gtk_target_list_unref ()
   from /usr/local/lib/libgtk-x11-2.0.so.0
#18 0x289671c4 in gtk_marshal_BOOLEAN__VOID ()
   from /usr/local/lib/libgtk-x11-2.0.so.0
#19 0x2911a767 in g_ptr_array_get_type ()
   from /usr/local/lib/libgobject-2.0.so.0
#20 0x2911bea3 in g_closure_invoke () from
/usr/local/lib/libgobject-2.0.so.0
#21 0x29133b58 in g_signal_handlers_block_matched ()
   from /usr/local/lib/libgobject-2.0.so.0
#22 0x29135706 in g_signal_emit_valist ()
   from /usr/local/lib/libgobject-2.0.so.0
#23 0x29135d45 in g_signal_emit () from
/usr/local/lib/libgobject-2.0.so.0
#24 0x28a8dc66 in gtk_widget_style_attach ()
   from /usr/local/lib/libgtk-x11-2.0.so.0
#25 0x289611e5 in gtk_main_do_event () from
/usr/local/lib/libgtk-x11-2.0.so.0
#26 0x28c49f1a in gdk_add_client_message_filter ()
   from /usr/local/lib/libgdk-x11-2.0.so.0
#27 0x291952d7 in g_main_context_dispatch ()
   from /usr/local/lib/libglib-2.0.so.0
#28 0x2919935e in g_main_context_prepare ()
   from /usr/local/lib/libglib-2.0.so.0
#29 0x29199767 in g_main_loop_run () from
/usr/local/lib/libglib-2.0.so.0
#30 0x289615c4 in gtk_main () from /usr/local/lib/libgtk-x11-2.0.so.0
#31 0x0806482b in ?? ()
#32 0x08064db1 in ?? ()
#33 0x08058a46 in ?? ()
#34 0x0001 in ?? ()
#35 0xbfbfe724 in ?? ()
#36 0xbfbfe72c in ?? ()
#37 0xbfbfe6d8 in ?? ()
#38 0x in ?? ()
#39 0x in ?? ()
#40 0x in ?? ()
#41 0xbfbfe710 in ?? ()
#42 0xbfbfe720 in ?? ()
#43 0x in ?? ()
#44 0xbfbfe71c in ?? ()
#45 0x080589c8 in ?? ()
Previous frame inner to this frame (corrupt stack?)

Does this help? Let me know if you need more info or want me test
changes in the source.

Thanks

matthias

-- 
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e g...@unixarea.de - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5
___
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 7.7 ready for testing!

2012-06-10 Thread Alexander Yerenkow
Is this fresh installation or you were upgrading?
I'm preparing now live image with new xorg, and don't saw such errors.
But I had yesterday's src/ports tree.


-- 
Regards,
Alexander Yerenkow
___
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 7.7 ready for testing!

2012-06-10 Thread Ivan Klymenko
В Sun, 10 Jun 2012 11:48:41 +0300
Alexander Yerenkow yeren...@gmail.com пишет:

 Is this fresh installation or you were upgrading?

of course updating

 I'm preparing now live image with new xorg, and don't saw such errors.
 But I had yesterday's src/ports tree.
 
 

___
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 7.7 ready for testing!

2012-06-10 Thread Ivan Klymenko
В Sun, 10 Jun 2012 11:48:41 +0300
Alexander Yerenkow yeren...@gmail.com пишет:

 Is this fresh installation or you were upgrading?
 I'm preparing now live image with new xorg, and don't saw such errors.
 But I had yesterday's src/ports tree.
 
 

Forgot to add - to svn r501 everything is fine build and working...
___
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: math/ess CONFLICTS with devel/noweb, help with CONFLICTS= needed

2012-06-10 Thread Christopher J. Ruwe
On Sat, 09 Jun 2012 21:16:04 +0200
Mel Flynn rfl...@acsalaska.net wrote:

 On 9-6-2012 14:02, Matthew Seaman wrote:
  On 09/06/2012 12:25, Christopher J. Ruwe wrote:
  Thanks for your quick answer. Incidentally, I am at this moment
  also preparing a maintainer update for a new version of math/ess.
  Should I perpare two PRs, one for the CONFLICTS and one for the
  actual update or is it permissable to pack these two into one?
  
  It is best to put all the changes you want to make into one PR.
  That will get it processed most efficiently.
 
 And if there's a PR for the conflict problem, then mention in your
 update PR that this update closes PR xx.
 

Thanks for reminding me, I would surely have forgotten. However, closing
another PR does not apply, I was approached using private mail by a
group apparently implementing something like a FreeBSD ports conflicts
checker, who are systematically combing the ports tree for conflicts not
yet known by the maintainers.

Some maintainer update PRs already adress problems thus found. 

Thanks, cheers, 
-- 
Christopher J. Ruwe
TZ: GMT + 1h


signature.asc
Description: PGP signature


Re: [CFT] Xorg 7.7 ready for testing!

2012-06-10 Thread Alexander Yerenkow
Okay everyone interested - listen up :)

http://gits.kiev.ua/FreeBSD/FreeBSD-10-i386-2012-06-08.img.xz

Here is the image, which can be dd'ed to 4g+ flash drive.
It should be bootable, and contains new xorg, and some soft from ports;
- seamonkey (if you want go to internet)
- stellarium (it's full of stars)
- blender (but it depends on devel/icu which probably built with
error, or by some other reason blender produces coredump)
- xterm and openbox;

How to use:
boot, login as root;
after passwordless login you can view simple x run script with:
cat ./runx.sh

or you just launch it
./runx.sh

If you have non-intel card, you need edit xorg.conf, and runx.sh
(remove load i915kms).
Load process and X launching can be a while if you have not very fast flash.

I'll continue improving of infrastructure for building such testing
images, helps and advises appreciated.

-- 
Regards,
Alexander Yerenkow
___
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: Documenting 'make config' options

2012-06-10 Thread Vitaly Magerya
Baptiste Daroussin b...@freebsd.org wrote:
 There was a PR[1] to use some dialog(1) feature to expose it to
 the user, would be nice if that extended description could
 implemented that way (using help button from dialog(1)) I do not
 plan to work on this now if someone want to do it that will be
 great

 1: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/123185

I'm attaching a simple patch that allows you to hit F1 and view
pkg-options-descr file in the options dialog (pkg- prefix
should probably be removed, as that file has nothing to do with
packages).
--- bsd.port.mk.orig2012-06-10 11:11:40.0 +0300
+++ bsd.port.mk 2012-06-10 12:15:44.0 +0300
@@ -2374,6 +2374,7 @@
 .endif
 
 DESCR?=${PKGDIR}/pkg-descr
+OPTIONS_DESCR?=${PKGDIR}/pkg-options-descr
 PLIST?=${PKGDIR}/pkg-plist
 PKGINSTALL?=   ${PKGDIR}/pkg-install
 PKGDEINSTALL?= ${PKGDIR}/pkg-deinstall
@@ -6068,8 +6069,15 @@
(${ECHO_MSG} === Cannot create $${optionsdir}, check permissions; 
exit 1)
 .endif
@TMPOPTIONSFILE=$$(mktemp -t portoptions); \
+   if [ -e ${OPTIONS_DESCR} ]; then \
+   helpopt=--hfile ${OPTIONS_DESCR}; \
+   helptitle= (F1 for details); \
+   else \
+   helpopt=; \
+   helptitle=; \
+   fi; \
trap ${RM} -f $${TMPOPTIONSFILE}; exit 1 1 2 3 5 10 13 15; \
-   ${DIALOG} --checklist Options for ${PKGNAME:C/-([^-]+)$/ \1/} 21 70 
15 ${DEFOPTIONS} 2 $${TMPOPTIONSFILE} || { \
+   ${DIALOG} $${helpopt} --checklist Options for ${PKGNAME:C/-([^-]+)$/ 
\1/}$${helptitle} 21 70 15 ${DEFOPTIONS} 2 $${TMPOPTIONSFILE} || { \
${RM} -f $${TMPOPTIONSFILE}; \
${ECHO_MSG} === Options unchanged; \
exit 0; \
___
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 7.7 ready for testing!

2012-06-10 Thread Andreas Nilsson
On Sun, Jun 10, 2012 at 11:13 AM, Ivan Klymenko fi...@ukr.net wrote:

 В Sun, 10 Jun 2012 11:48:41 +0300
 Alexander Yerenkow yeren...@gmail.com пишет:

  Is this fresh installation or you were upgrading?
  I'm preparing now live image with new xorg, and don't saw such errors.
  But I had yesterday's src/ports tree.
 
 

 Forgot to add - to svn r501 everything is fine build and working...


I checked out the xorg repo yesterday and it built just fine ( on
9.0-RELEASE with  drm-all.14.5-releng9.0.patch ). I actually did this in a
clone of my root-dataset so I started with pkg_delete -a :) )

Just a thought: shouldn't the new intel driver be part of the OPTIONS of
the new xorg-drivers?

I'll write back with the results when I get back into the office.

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


make {run,build}-depends-list vs. pkg_info -r?

2012-06-10 Thread Ben Laurie
I am confused...

In audio/squeezecenter, I get:

# make {run,build}-depends-list
/usr/ports/archivers/p5-Compress-Zlib
/usr/ports/audio/faad
/usr/ports/audio/flac
/usr/ports/audio/mac
/usr/ports/audio/sox
/usr/ports/converters/p5-Encode-Detect
/usr/ports/converters/p5-JSON-XS
/usr/ports/databases/mysql50-client
/usr/ports/databases/mysql50-server
/usr/ports/databases/p5-DBD-mysql
/usr/ports/devel/p5-Time-HiRes
/usr/ports/graphics/p5-GD
/usr/ports/lang/perl5.8
/usr/ports/net/mDNSResponder
/usr/ports/security/p5-Digest-SHA1
/usr/ports/textproc/p5-XML-Parser
/usr/ports/textproc/p5-YAML-Syck
/usr/ports/www/p5-HTML-Parser
/usr/ports/www/p5-Template-Toolkit
/usr/ports/databases/mysql50-client
/usr/ports/lang/perl5.8
/usr/ports/sysutils/p5-File-Which

but:

# pkg_info -r squeezecenter-7.3.3
Information for squeezecenter-7.3.3:

Depends on:
Dependency: expat-2.0.1_2
Dependency: openssl-1.0.1_2
Dependency: mDNSResponder-333.10
Dependency: mp4v2-1.9.1
Dependency: libvpx-1.0.0
Dependency: perl-5.8.9_7
Dependency: p5-YAML-Syck-1.19
Dependency: p5-XML-Parser-2.41
Dependency: p5-HTML-Tagset-3.20
Dependency: p5-HTML-Parser-3.69
Dependency: p5-Digest-SHA1-2.13
Dependency: png-1.5.10
Dependency: jpeg-8_3
Dependency: gpac-libgpac-0.4.5_6,1
Dependency: x264-0.123.2189_2
Dependency: pkg-config-0.25_1
Dependency: opencv-core-2.3.1_4
Dependency: freetype2-2.4.9_1
Dependency: gd-2.0.35_8,1
Dependency: p5-GD-2.46_1
Dependency: p5-common-sense-3.4
Dependency: p5-Time-HiRes-1.9725,1
Dependency: p5-AppConfig-1.66
Dependency: p5-Template-Toolkit-2.24
Dependency: orc-0.4.16
Dependency: schroedinger-1.0.11
Dependency: libltdl-2.4.2
Dependency: p5-DBI-1.621
Dependency: mysql-client-5.0.95
Dependency: p5-DBD-mysql-4.021
Dependency: mysql-server-5.0.95
Dependency: p5-JSON-XS-2.32
Dependency: p5-Encode-Detect-1.01
Dependency: libiconv-1.14
Dependency: mac-3.99.4.5_1
Dependency: libogg-1.2.2,4
Dependency: libvorbis-1.3.3,3
Dependency: libtheora-1.1.1_2
Dependency: libmad-0.15.1b_2
Dependency: libid3tag-0.15.1b
Dependency: libao-1.1.0_1
Dependency: lame-3.99.5
Dependency: gsm-1.0.13
Dependency: flac-1.2.1_2
Dependency: libsndfile-1.0.25_1
Dependency: faad2-2.7_3,1
Dependency: faac-1.28_2
Dependency: ffmpeg-0.7.12_2,1
Dependency: sox-14.3.2_4
Dependency: p5-IO-Compress-Base-2.015
Dependency: p5-Compress-Raw-Zlib-2.054
Dependency: p5-IO-Compress-Zlib-2.015_1
Dependency: p5-Compress-Zlib-2.015

Why are the dependencies so different? e.g. the p5*Compress* ones...

What's going on?
___
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: make {run,build}-depends-list vs. pkg_info -r?

2012-06-10 Thread Julien Laffaye

On 6/10/2012 1:22 PM, Ben Laurie wrote:

I am confused...

In audio/squeezecenter, I get:

# make {run,build}-depends-list
/usr/ports/archivers/p5-Compress-Zlib
/usr/ports/audio/faad
/usr/ports/audio/flac
/usr/ports/audio/mac
/usr/ports/audio/sox
/usr/ports/converters/p5-Encode-Detect
/usr/ports/converters/p5-JSON-XS
/usr/ports/databases/mysql50-client
/usr/ports/databases/mysql50-server
/usr/ports/databases/p5-DBD-mysql
/usr/ports/devel/p5-Time-HiRes
/usr/ports/graphics/p5-GD
/usr/ports/lang/perl5.8
/usr/ports/net/mDNSResponder
/usr/ports/security/p5-Digest-SHA1
/usr/ports/textproc/p5-XML-Parser
/usr/ports/textproc/p5-YAML-Syck
/usr/ports/www/p5-HTML-Parser
/usr/ports/www/p5-Template-Toolkit
/usr/ports/databases/mysql50-client
/usr/ports/lang/perl5.8
/usr/ports/sysutils/p5-File-Which

but:

# pkg_info -r squeezecenter-7.3.3
Information for squeezecenter-7.3.3:

Depends on:
Dependency: expat-2.0.1_2
Dependency: openssl-1.0.1_2
Dependency: mDNSResponder-333.10
Dependency: mp4v2-1.9.1
Dependency: libvpx-1.0.0
Dependency: perl-5.8.9_7
Dependency: p5-YAML-Syck-1.19
Dependency: p5-XML-Parser-2.41
Dependency: p5-HTML-Tagset-3.20
Dependency: p5-HTML-Parser-3.69
Dependency: p5-Digest-SHA1-2.13
Dependency: png-1.5.10
Dependency: jpeg-8_3
Dependency: gpac-libgpac-0.4.5_6,1
Dependency: x264-0.123.2189_2
Dependency: pkg-config-0.25_1
Dependency: opencv-core-2.3.1_4
Dependency: freetype2-2.4.9_1
Dependency: gd-2.0.35_8,1
Dependency: p5-GD-2.46_1
Dependency: p5-common-sense-3.4
Dependency: p5-Time-HiRes-1.9725,1
Dependency: p5-AppConfig-1.66
Dependency: p5-Template-Toolkit-2.24
Dependency: orc-0.4.16
Dependency: schroedinger-1.0.11
Dependency: libltdl-2.4.2
Dependency: p5-DBI-1.621
Dependency: mysql-client-5.0.95
Dependency: p5-DBD-mysql-4.021
Dependency: mysql-server-5.0.95
Dependency: p5-JSON-XS-2.32
Dependency: p5-Encode-Detect-1.01
Dependency: libiconv-1.14
Dependency: mac-3.99.4.5_1
Dependency: libogg-1.2.2,4
Dependency: libvorbis-1.3.3,3
Dependency: libtheora-1.1.1_2
Dependency: libmad-0.15.1b_2
Dependency: libid3tag-0.15.1b
Dependency: libao-1.1.0_1
Dependency: lame-3.99.5
Dependency: gsm-1.0.13
Dependency: flac-1.2.1_2
Dependency: libsndfile-1.0.25_1
Dependency: faad2-2.7_3,1
Dependency: faac-1.28_2
Dependency: ffmpeg-0.7.12_2,1
Dependency: sox-14.3.2_4
Dependency: p5-IO-Compress-Base-2.015
Dependency: p5-Compress-Raw-Zlib-2.054
Dependency: p5-IO-Compress-Zlib-2.015_1
Dependency: p5-Compress-Zlib-2.015

Why are the dependencies so different? e.g. the p5*Compress* ones...

What's going on?

pkg_info shows the complete dependencies, and not only the direct 
dependencies.

___
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


gnash-0.8.9_4 compiler error

2012-06-10 Thread Denk Padje
gnash-0.8.9_4 fails to compile on FreeBSD 9.0-RELEASE

Options: PLUGIN, GTK, AGG, FFMPEG
Installed dependency: ffmpeg-devel-2012.04.25_2

Don't know if this is due to having installed ffmpeg-devel instead of old
ffmpeg, but the package manager was fine with it.

libtool: compile:  c++ -DHAVE_CONFIG_H -I. -I.. -I../libbase -D_THREAD_SAFE
-pthread -I/usr/local/include/libpng -I/usr/local/include/glib-2.0
-I/usr/local/include/glib-2.0 -I/usr/local/include -DCURL_STATICLIB
-I/usr/local/include -I/usr/local/include -I/usr/local/include
-D__STDC_CONSTANT_MACROS -I/usr/local/include -I/usr/local/include
-I/usr/local/include/speex -I/usr/local/include -I../libvaapi
-DREGISTER_MEDIA_HANDLERS -O2 -fno-strict-aliasing -pipe -march=pentium-m
-W -Wall -Wcast-align -Wcast-qual -Wpointer-arith -Wreturn-type
-Wnon-virtual-dtor -Wunused -fvisibility-inlines-hidden -MT
libgnashmedia_la-MediaHandlerFfmpeg.lo -MD -MP -MF
.deps/libgnashmedia_la-MediaHandlerFfmpeg.Tpo -c
ffmpeg/MediaHandlerFfmpeg.cpp  -fPIC -DPIC -o
.libs/libgnashmedia_la-MediaHandlerFfmpeg.o
In file included from
/usr/local/include/boost/type_traits/aligned_storage.hpp:11,
 from /usr/local/include/boost/type_traits.hpp:20,
 from ../libbase/GnashFactory.h:32,
 from ./MediaHandler.h:26,
 from ffmpeg/MediaHandlerFfmpeg.h:22,
 from ffmpeg/MediaHandlerFfmpeg.cpp:21:
/usr/local/include/boost/aligned_storage.hpp:90: warning: enumeral and
non-enumeral type in conditional expression
In file included from ffmpeg/MediaHandlerFfmpeg.cpp:26:
ffmpeg/MediaParserFfmpeg.h:152: error: 'ByteIOContext' does not name a type
ffmpeg/MediaParserFfmpeg.h:170: error: 'SampleFormat' has not been declared
gmake[2]: *** [libgnashmedia_la-MediaHandlerFfmpeg.lo] Error 1
gmake[2]: Leaving directory
`/usr/ports/graphics/gnash/work/gnash-0.8.9/libmedia'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/graphics/gnash/work/gnash-0.8.9'
gmake: *** [all] Error 2
*** Error code 1

Stop in /usr/ports/graphics/gnash.
*** Error code 1

Stop in /usr/ports/graphics/gnash.

=== make failed for graphics/gnash
=== Aborting update

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


Removing hal dependency of x11-drivers/xf86-input-synaptics

2012-06-10 Thread David Demelier

Hi,

After 4 or 5 emails sent to miwi@ I think Martin just ignore me. It's 
about a commit for removing a useless HAL dependency added a few weeks ago.


In fact, x11-drivers/xf86-input-synaptics may install an old and useless 
HAL file (.fdi), I have no problem with that, but a RUN_DEPENDS
variable has been added against HAL and we need to install HAL and about 
30 pulled in depencies.


Here's the PR to remove this HAL dependency:

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/167533

Please commit it,
Cheers.

--
David Demelier
___
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: Removing hal dependency of x11-drivers/xf86-input-synaptics

2012-06-10 Thread Michael Scheidell



On 6/10/12 7:07 AM, David Demelier wrote:

Hi,

In fact, x11-drivers/xf86-input-synaptics may install an old and 
useless HAL file (.fdi), I have no problem with that, but a RUN_DEPENDS
variable has been added against HAL and we need to install HAL and 
about 30 pulled in depencies.


Here's the PR to remove this HAL dependency:

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/167533
It may be that something that you don't use needs HAL.  so wait? x11 
(and the new 7.5.2) needs a good shakeout.
Additionally, adding an options knob (especially one that changes the 
default packaging), is usually done if there is significant call for it.
Adding an option knob makes a build, rebuild, or upgrade stop in one 
more place would require a real need.


(yes, 30 dependencies would be one indicator), second indicator would be 
that (some) packages are broken without it.
Also, changing the default will change the default package distributed 
by FreeBSD on clusters.


either wait for miwi, and/or always when adding an option knob keep the 
default behavior.


(ps, did you rebuild and test  x11/gsynaptics without HAL ?



--
Michael Scheidell, CTO
*| * SECNAP Network Security Corporation
d: +1.561.948.2259
w: http://people.freebsd.org/~scheidell
___
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


opengtl 0.9.17

2012-06-10 Thread ajtiM
On my FreeBSD 9.0-Release building of openglt-0.9.17 doesn't work with gcc 4.6 
and with clan 3.0:
/usr/ports/graphics/opengtl/work/OpenGTL-0.9.17/OpenGTL/GTLCore/StdTypes.h:93:7:
 
warning: no newline at end of file
/usr/ports/graphics/opengtl/work/OpenGTL-0.9.17/OpenGTL/GTLCore/LLVMBackend/CodeGenerator_p.cpp:
 
In static member function 'static llvm::Constant* 
LLVMBackend::CodeGenerator::stringToConstant(llvm::LLVMContext, const 
GTLCore::String)':
/usr/ports/graphics/opengtl/work/OpenGTL-0.9.17/OpenGTL/GTLCore/LLVMBackend/CodeGenerator_p.cpp:1244:
 
error: 'llvm::ConstantDataArray' has not been declared
*** Error code 1
[ 42%] Building CXX object 
OpenGTL/GTLCore/CMakeFiles/GTLCore.dir/LLVMBackend/ExpressionResult_p.cpp.o
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 1

Stop in /usr/ports/graphics/opengtl.
*** Error code 1

Stop in /usr/ports/graphics/opengtl.

=== make failed for graphics/opengtl
=== Aborting update


Mitja

http://jpgmag.com/people/lumiwa
___
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


pkgng crashes in make install.

2012-06-10 Thread George Liaskos
Hello,

Under 9.0-RELEASE i386 the latest pkg from ports almost always crashes
on me when running make install in a port directory.

#0  0x282d8ca7 in sbuf_cat () from /lib/libsbuf.so.6
#1  0x282d8d01 in sbuf_cpy () from /lib/libsbuf.so.6
#2  0x280b9269 in sbuf_set (buf=0x2880e104, str=0x3 Address 0x3 out
of bounds) at utils.c:61
#3  0x280ca8d0 in pkg_vset (pkg=0x2880e100, ap=0xbfbfe100 ) at pkg.c:269
#4  0x280caa61 in pkg_set2 (pkg=0x2880e100) at pkg.c:312
#5  0x08052ca3 in exec_register (argc=7, argv=0xbfbfea5c) at register.c:122
#6  0x0804fc61 in main (argc=7, argv=0xbfbfea5c) at main.c:313


Regards,
George
___
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: libreoffice, Makefile fix proposal...

2012-06-10 Thread Lawrence K. Chen, P.Eng.


- Original Message -
 2012/6/7 Sergio de Almeida Lenzi lenzi.ser...@gmail.com:
  Well, now that libreoffice build is
  solved, than  what about insert
  a line:
  CONFLICTS_BUILD=    boost*
  near line 63 of Makefile???
 
 libreoffice does not conflict with boost;
 just Makefile has a problem.
 
 Attached is the patch.

This patch didn't work for me.

So, I tried the:

# portmaster -g boost-libs boost-jam
# pkg_delete -f boost-libs-\* boost-jam-\*
# postmaster libreoffice
# portmaster -PP --local-packagedir=/usr/ports/packages boost-libs boost-jam
 or
use pkg_add

portmaster libreoffice didn't work...it got stuck

=== Waiting on fetch  checksum for editors/libreoffice ===
=== Waiting on fetch  checksum for editors/libreoffice ===
=== Waiting on fetch  checksum for editors/libreoffice ===
=== Waiting on fetch  checksum for editors/libreoffice ===
=== Waiting on fetch  checksum for editors/libreoffice ===

ended up doing make deinstall reinstall clean

And, then couldn't use portmaster to get boost-libs boost-jam backso used 
pkg_add.

However, that was on my home machine.  I then tried to do the same on a system 
at workand it complained that boost wasn't installed in the configure, 
h...oh nevermind.  Somebody had set 'CONFIGURE_ARGS=--with-system-boost' 
in make.conf.  Guess I'l try my steps again

-- 
Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator
For: Enterprise Server Technologies (EST) --  SafeZone Ally
Snail: Computing and Telecommunications Services (CTS)
Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102
Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkc...@ksu.edu
Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library
___
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] gdal 1.9.1 update and other changes

2012-06-10 Thread coder.tuxfamily

Le 09.06.2012 08:49, coder.tuxfamily a écrit :

Le 07.06.2012 15:52, Frank Broniewski a écrit :

Yes, that worked.

I tested it with py-gdal. First I had some problems because there were
some other programs depending gdal-grass (QGIS, Grass GIS) which linked
to the older gdal libs, but after deleting gdal-grass, I could import
the module into python and run successfully some tests against some
scripts I had written.



Thank you for the works. I will make tests today with all my
scritps/plugins.

Just a few remarks for now :

- graphics/gdal
Maybe add this options :
 ARMADILLOFaster TPS transform computation
CONFIGURE_ARGS+=--with-armadillo=yes

 FREEXLFreeXL support
LIB_DEPENDS+=freexl:${PORTSDIR}/textproc/freexl
CONFIGURE_ARGS+=--with-freexl=${LOCALBASE}

 MDBInclude MDB driver (need Java)
CONFIGURE_ARGS+=--with-mdb --with-java= ; Maybe with java bindings ?

For PDF (Poppler OR podofo)
 POPPLERPoppler support (for PDF)
LIB_DEPENDS+=poppler:${PORTSDIR}/graphics/poppler
CONFIGURE_ARGS+=--with-poppler=${LOCALBASE}

 PODOFOPoDoFo support (for PDF)
LIB_DEPENDS+=podofo:${PORTSDIR}/graphics/podofo
CONFIGURE_ARGS+=--with-podofo=${LOCALBASE}
--with-podofo-lib=${LOCALBASE}/lib

 SPATIALITESpatialite support
CONFIGURE_ARGS+=--with-spatialite=${LOCALBASE}


I'm working for the other options, but need add some ports (libgdata ;
ogdi ; ESRI GDB Api ; RASDAMAN)


Is it possible to add bindings options directly into graphics/gdal ?


For other bindings :
Maybe add java bindings (for MDB protocol, very useful)

For QGIS port (and maybe other like Grass)
Will need adding py-gdal when python is checked (used by plugins
GdalTools ; fTools ; openlayers ; GoogleLayers ... and many others)


Your works is very helpful thank you !

___
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


My scripts/softs works fine with the new version.
___
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: Imagemagick: FAIL, now in Magick++/demo/analyze.sh

2012-06-10 Thread Kevin Oberman
On Sat, Jun 9, 2012 at 8:02 PM, Doug Barton do...@freebsd.org wrote:
 The new version fails in a new location, even with the default options.


Was this an amd64 system? All of my i386 systems installed the new
ImageMagick cleanly, but my only amd64 system hit this.
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.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: Imagemagick: FAIL, now in Magick++/demo/analyze.sh

2012-06-10 Thread Rainer Hurling

On 10.06.2012 18:19 (UTC+2), Kevin Oberman wrote:

On Sat, Jun 9, 2012 at 8:02 PM, Doug Barton do...@freebsd.org wrote:

The new version fails in a new location, even with the default options.



Was this an amd64 system? All of my i386 systems installed the new
ImageMagick cleanly, but my only amd64 system hit this.


Yes, for me too, it fails on CURRENT amd64 system.
___
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


WAS: Re: Why Are You NOT Using FreeBSD ? New: port annoyance LibreOffice

2012-06-10 Thread O. Hartmann
On 06/10/12 17:43, John Merryweather Cooper wrote:
 On 06/10/12 09:54, Martin Sugioarto wrote:
 Am Sun, 10 Jun 2012 11:37:09 +0100
 schrieb Chris Reescr...@freebsd.org:

 Er... people always test their commits.  Sometimes edge cases will
 creep in, such as the libreoffice failure which was due to different
 configurations, but to suggest that the commit wasn't tested is quite
 frankly insulting-- it built on a clean system perfectly well.
 Hi,

 I don't mean to insult anyone. As I have already told, I am really
 thankful that people invest their precious time into updating the ports
 collection.

 Whatever clean system means. It is surely not the default case that
 someone has got a freshly installed set of ports.

 Among all the default problems with ports, libreoffice[1] adds to the
 group of annoyances[2] at the moment. I don't know when I have seen
 portmaster -ad run through successfully last time. I need more and
 more -x options to exclude ports which fail to build.

 [1] german/libreoffice and libreoffice fails all the time in
 (LOCALIZED_LANG is set to de):

 Module 'lingucomponent' delivered successfully. 12 files copied, 2
 files unchanged

 ---
  Oh dear - something failed during the build - sorry !
For more help with debugging build errors, please see the section in:
  http://wiki.documentfoundation.org/Development

internal build errors:

 ERROR: error 65280 occurred while
 making
 /usr/workdir-ports/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj


   it seems that the error is inside 'vcl', please re-run build
   inside this module to isolate the error and/or test your fix:
 ---


 Whatever this tries to tell me. I don't get it. This is a completely
 useless error message for me.

Not even in german/libreoffice. i try to build the standard version and
I receive the same error.

I can fix this by doing what the buildsystem suggests, but then I have a
stop in sfx2 and others and it ends up in some module called tail_,
where the build never ends when performing the repair as suggested. I
had once a box running all the night looping building in this folder.


 [2] The default annoyances are for example:

 - After updating perl, php or whatever, it makes sense to enforce
updating the modules that belong to these ports. I've seen 100x the
same message that p5-XML-Parser does not work and know what it means,
but this should be resolved by the port system. I mean, when you
update perl, the perl modules won't work anymore. This is totally
clear and it makes sense to update them first before going on.

I can confirm that. I fixed that for me by portmaster p5- in case
p5-SAX-XXX failed.


 - When specifying WITHOUT_X11 the ports should respect this and not try
to pull in the X11 variants of ports. I regularly see some ports
pulling ImageMagick instead of the already installed
ImageMagick-nox11. I still do not fully understand what is going on
with WITHOUT_GNOME, but I'll try to figure it out later. But I am
quite sure that some ports pull in unneeded Gnome dependencies.

 - Ports are being marked as interactive and stop the update process. The
idea behind portmaster was (earlier) to avoid interactive building of
ports and ask all the needed questions, before the builds start. I
mean, earlier, I could get out and enjoy some coffee outdoors, now I
have to sit at the keyboard. This is unacceptable! ;)

portmaster does even more damage. Sometimed a port reels in some newly
updates, a port gets deleted. if on of the to be updated prerquisits
fail, the port in question isn't there anymore.

portmaster fails quite often in oberwriting remnant files. If a port
gets corrupted by accident, like graphics/netpbm, One need to delete all
binaries manually from /usr/local/bin, otherwise the installation fails.

Somehow I wish to have a brute force knob to overwrite everything in a
brutal way.


 - It would be nice to have a mechanism that tells you that your perl,
mysql or whatever is not the default version anymore and you should
consider updating to the default (and recommended) port.


 Martin
 
 From /etc/defaults/periodic.conf:
 
 # 400.status-pkg
 weekly_status_pkg_enable=YES# Find out-of-date pkgs
 pkg_version=pkg_version   # Use this program
 pkg_version_index=/usr/ports/INDEX-9  # Use this index file
 
 There's an override script in ports-mgmt/portupgrade that uses it's
 database, also.
 



signature.asc
Description: OpenPGP digital signature


Re: WAS: Re: Why Are You NOT Using FreeBSD ? New: port annoyance LibreOffice

2012-06-10 Thread Chris Rees
On 10 June 2012 18:10, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
 On 06/10/12 17:43, John Merryweather Cooper wrote:
 On 06/10/12 09:54, Martin Sugioarto wrote:
 Am Sun, 10 Jun 2012 11:37:09 +0100
 schrieb Chris Reescr...@freebsd.org:

 Er... people always test their commits.  Sometimes edge cases will
 creep in, such as the libreoffice failure which was due to different
 configurations, but to suggest that the commit wasn't tested is quite
 frankly insulting-- it built on a clean system perfectly well.
 Hi,

 I don't mean to insult anyone. As I have already told, I am really
 thankful that people invest their precious time into updating the ports
 collection.

 Whatever clean system means. It is surely not the default case that
 someone has got a freshly installed set of ports.

 Among all the default problems with ports, libreoffice[1] adds to the
 group of annoyances[2] at the moment. I don't know when I have seen
 portmaster -ad run through successfully last time. I need more and
 more -x options to exclude ports which fail to build.

 [1] german/libreoffice and libreoffice fails all the time in
 (LOCALIZED_LANG is set to de):

 Module 'lingucomponent' delivered successfully. 12 files copied, 2
 files unchanged

 ---
          Oh dear - something failed during the build - sorry !
    For more help with debugging build errors, please see the section in:
              http://wiki.documentfoundation.org/Development

    internal build errors:

 ERROR: error 65280 occurred while
 making
 /usr/workdir-ports/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj


   it seems that the error is inside 'vcl', please re-run build
   inside this module to isolate the error and/or test your fix:
 ---


 Whatever this tries to tell me. I don't get it. This is a completely
 useless error message for me.

 Not even in german/libreoffice. i try to build the standard version and
 I receive the same error.

 I can fix this by doing what the buildsystem suggests, but then I have a
 stop in sfx2 and others and it ends up in some module called tail_,
 where the build never ends when performing the repair as suggested. I
 had once a box running all the night looping building in this folder.


 [2] The default annoyances are for example:

 - After updating perl, php or whatever, it makes sense to enforce
    updating the modules that belong to these ports. I've seen 100x the
    same message that p5-XML-Parser does not work and know what it means,
    but this should be resolved by the port system. I mean, when you
    update perl, the perl modules won't work anymore. This is totally
    clear and it makes sense to update them first before going on.

 I can confirm that. I fixed that for me by portmaster p5- in case
 p5-SAX-XXX failed.

There's an UPDATING message written for that very purpose.


 - When specifying WITHOUT_X11 the ports should respect this and not try
    to pull in the X11 variants of ports. I regularly see some ports
    pulling ImageMagick instead of the already installed
    ImageMagick-nox11. I still do not fully understand what is going on
    with WITHOUT_GNOME, but I'll try to figure it out later. But I am
    quite sure that some ports pull in unneeded Gnome dependencies.

 - Ports are being marked as interactive and stop the update process. The
    idea behind portmaster was (earlier) to avoid interactive building of
    ports and ask all the needed questions, before the builds start. I
    mean, earlier, I could get out and enjoy some coffee outdoors, now I
    have to sit at the keyboard. This is unacceptable! ;)

 portmaster does even more damage. Sometimed a port reels in some newly
 updates, a port gets deleted. if on of the to be updated prerquisits
 fail, the port in question isn't there anymore.

 portmaster fails quite often in oberwriting remnant files. If a port
 gets corrupted by accident, like graphics/netpbm, One need to delete all
 binaries manually from /usr/local/bin, otherwise the installation fails.

 Somehow I wish to have a brute force knob to overwrite everything in a
 brutal way.

FORCE_PKG_REGISTER.


 - It would be nice to have a mechanism that tells you that your perl,
    mysql or whatever is not the default version anymore and you should
    consider updating to the default (and recommended) port.


 Martin

 From /etc/defaults/periodic.conf:

 # 400.status-pkg
 weekly_status_pkg_enable=YES                # Find out-of-date pkgs
 pkg_version=pkg_version                           # Use this program
 pkg_version_index=/usr/ports/INDEX-9      # Use this index file

 There's an override script in ports-mgmt/portupgrade that uses it's
 database, also.


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any 

Re: WAS: Re: Why Are You NOT Using FreeBSD ? New: port annoyance LibreOffice

2012-06-10 Thread O. Hartmann
On 06/10/12 19:20, Chris Rees wrote:
 On 10 June 2012 18:10, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
 On 06/10/12 17:43, John Merryweather Cooper wrote:
 On 06/10/12 09:54, Martin Sugioarto wrote:
 Am Sun, 10 Jun 2012 11:37:09 +0100
 schrieb Chris Reescr...@freebsd.org:

 Er... people always test their commits.  Sometimes edge cases will
 creep in, such as the libreoffice failure which was due to different
 configurations, but to suggest that the commit wasn't tested is quite
 frankly insulting-- it built on a clean system perfectly well.
 Hi,

 I don't mean to insult anyone. As I have already told, I am really
 thankful that people invest their precious time into updating the ports
 collection.

 Whatever clean system means. It is surely not the default case that
 someone has got a freshly installed set of ports.

 Among all the default problems with ports, libreoffice[1] adds to the
 group of annoyances[2] at the moment. I don't know when I have seen
 portmaster -ad run through successfully last time. I need more and
 more -x options to exclude ports which fail to build.

 [1] german/libreoffice and libreoffice fails all the time in
 (LOCALIZED_LANG is set to de):

 Module 'lingucomponent' delivered successfully. 12 files copied, 2
 files unchanged

 ---
  Oh dear - something failed during the build - sorry !
For more help with debugging build errors, please see the section in:
  http://wiki.documentfoundation.org/Development

internal build errors:

 ERROR: error 65280 occurred while
 making
 /usr/workdir-ports/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj


   it seems that the error is inside 'vcl', please re-run build
   inside this module to isolate the error and/or test your fix:
 ---


 Whatever this tries to tell me. I don't get it. This is a completely
 useless error message for me.

 Not even in german/libreoffice. i try to build the standard version and
 I receive the same error.

 I can fix this by doing what the buildsystem suggests, but then I have a
 stop in sfx2 and others and it ends up in some module called tail_,
 where the build never ends when performing the repair as suggested. I
 had once a box running all the night looping building in this folder.


 [2] The default annoyances are for example:

 - After updating perl, php or whatever, it makes sense to enforce
updating the modules that belong to these ports. I've seen 100x the
same message that p5-XML-Parser does not work and know what it means,
but this should be resolved by the port system. I mean, when you
update perl, the perl modules won't work anymore. This is totally
clear and it makes sense to update them first before going on.

 I can confirm that. I fixed that for me by portmaster p5- in case
 p5-SAX-XXX failed.
 
 There's an UPDATING message written for that very purpose.

And even WITH this message written in /usr/ports/UPDATING and follwoing
those instrauctions, I have had the very same problem as for years now
with this port.

The problem is, if you'd like to do an automated or unattended
update of the ports, you stumble very quickly in such a kind of show
stopper.

If you do not update on a regular basis, those problems develop in
very serious problems.

By the way, the reason why I update also the ports on a regular basis IS
because of 100% sure problems if I wait for weeks or months.

 

 - When specifying WITHOUT_X11 the ports should respect this and not try
to pull in the X11 variants of ports. I regularly see some ports
pulling ImageMagick instead of the already installed
ImageMagick-nox11. I still do not fully understand what is going on
with WITHOUT_GNOME, but I'll try to figure it out later. But I am
quite sure that some ports pull in unneeded Gnome dependencies.

 - Ports are being marked as interactive and stop the update process. The
idea behind portmaster was (earlier) to avoid interactive building of
ports and ask all the needed questions, before the builds start. I
mean, earlier, I could get out and enjoy some coffee outdoors, now I
have to sit at the keyboard. This is unacceptable! ;)

 portmaster does even more damage. Sometimed a port reels in some newly
 updates, a port gets deleted. if on of the to be updated prerquisits
 fail, the port in question isn't there anymore.

 portmaster fails quite often in oberwriting remnant files. If a port
 gets corrupted by accident, like graphics/netpbm, One need to delete all
 binaries manually from /usr/local/bin, otherwise the installation fails.

 Somehow I wish to have a brute force knob to overwrite everything in a
 brutal way.
 
 FORCE_PKG_REGISTER.

Enabled by default in /etc/make.conf in my configuration.

 And the problem still persists ...



signature.asc
Description: OpenPGP digital signature


Re: firefox 13.0,1 needs lang/gcc46 -- to RUN?!

2012-06-10 Thread Alan Hicks

On 08/06/2012 15:12, Alan Hicks wrote:

On 08/06/2012 11:09, Heino Tiedemann wrote:

Maciej Suszkomac...@suszko.eu wrote:


Heino Tiedemannrotkaps_spam_t...@gmx.de wrote:


What ist the meaning of

,
| Use GCC 4.6 to fix build on newer FreeBSD versions
`


What meians newer FreeBSD versions here?
http://www.freshports.org/www/firefox/


And what means

,
| Don't depend on GCC 4.6 if clang is used
`


How an I use clang?
http://www.freshports.org/www/firefox/



I just simply built www/firefox with those flags to make:
CC=clang CXX=clang++ CPP=clang-cpp

If you use portupgrade, this should work:
portupgrade -m 'CC=clang CXX=clang++ CPP=clang-cpp' firefox\*


does not work :(

clang++ -o nsUTF8UtilsSSE2.o -c -fvisibility=hidden
-DMOZ_GLUE_IN_PROGRAM -DMOZILLA_INTERNlude
-I../../../dist/include/nsprpub -I/usr/local/include
-I/usr/local/include/nspr -I/usr -I/usr/local/include -fno-rtti
-Qunused-arguments -Wall -Wpointer-arith -Woverloaded-virtid-offsetof
-Wno-variadic-macros -Werror=return-type -Wno-unknown-warning-option
-Wno-retur-std=gnu++0x -ffunction-sections -fdata-sections -pipe
-DNDEBUG -DTRIMMED -fno-omit-frame-/../../mozilla-config.h
/usr/ports/www/firefox/work/mozilla-release/xpcom/string/src/nsUTF8
In file included from
/usr/ports/www/firefox/work/mozilla-release/xpcom/string/src/nsUTF8UtilsSSE2.cpp:3:

In file included from /usr/include/clang/3.0/emmintrin.h:31:
In file included from /usr/include/clang/3.0/xmmintrin.h:31:
/usr/include/clang/3.0/mmintrin.h:28:2: error: #error MMX instruction
set not enabled
#error MMX instruction set not enabled
^
In file included from
/usr/ports/www/firefox/work/mozilla-release/xpcom/string/src/nsUTF8UtilsSSE2.cpp:3:

In file included from /usr/include/clang/3.0/emmintrin.h:31:
/usr/include/clang/3.0/xmmintrin.h:417:19: error: unknown type name
'__m64'
static __inline__ __m64 __attribute__((__always_inline__, __nodebug__))
^
/usr/include/clang/3.0/xmmintrin.h:417:25: error: expected unqualified-id
static __inline__ __m64 __attribute__((__always_inline__, __nodebug__))
^
In file included from
/usr/ports/www/firefox/work/mozilla-release/xpcom/string/src/nsUTF8UtilsSSE2.cpp:3:

/usr/include/clang/3.0/emmintrin.h:42:19: error: unknown type name
'__m128d'
static __inline__ __m128d __attribute__((__always_inline__, __nodebug__))
^
/usr/include/clang/3.0/emmintrin.h:42:27: error: expected unqualified-id
static __inline__ __m128d __attribute__((__always_inline__, __nodebug__))
^
In file included from
/usr/ports/www/firefox/work/mozilla-release/xpcom/string/src/nsUTF8UtilsSSE2.cpp:4:

../../../dist/include/nsUTF8Utils.h:90:10: error: use of undeclared
identifier 'UTF8traits'
if ( UTF8traits::isASCII(c) )
^
../../../dist/include/nsUTF8Utils.h:146:10: error: use of undeclared
identifier 'UTF8traits'
if ( UTF8traits::is2byte(c) )
^
../../../dist/include/nsUTF8Utils.h:152:15: error: use of undeclared
identifier 'UTF8traits'
else if ( UTF8traits::is3byte(c) )
^
../../../dist/include/nsUTF8Utils.h:158:15: error: use of undeclared
identifier 'UTF8traits'
else if ( UTF8traits::is4byte(c) )
^
../../../dist/include/nsUTF8Utils.h:164:15: error: use of undeclared
identifier 'UTF8traits'
else if ( UTF8traits::is5byte(c) )
^
../../../dist/include/nsUTF8Utils.h:170:15: error: use of undeclared
identifier 'UTF8traits'
else if ( UTF8traits::is6byte(c) )
^
../../../dist/include/nsUTF8Utils.h:186:10: error: use of undeclared
identifier 'UTF8traits'
if ( UTF8traits::isInSeq(c) )
^
../../../dist/include/nsUTF8Utils.h:393:18: error: use of undeclared
identifier 'UTF8traits'
if ( UTF8traits::isASCII(*p) )
^
../../../dist/include/nsUTF8Utils.h:395:23: error: use of undeclared
identifier 'UTF8traits'
else if ( UTF8traits::is2byte(*p) )
^
../../../dist/include/nsUTF8Utils.h:397:23: error: use of undeclared
identifier 'UTF8traits'
else if ( UTF8traits::is3byte(*p) )
^
../../../dist/include/nsUTF8Utils.h:399:23: error: use of undeclared
identifier 'UTF8traits'
else if ( UTF8traits::is4byte(*p) ) {
^
../../../dist/include/nsUTF8Utils.h:442:23: error: use of undeclared
identifier 'UTF8traits'
else if ( UTF8traits::is5byte(*p) )
^
../../../dist/include/nsUTF8Utils.h:444:23: error: use of undeclared
identifier 'UTF8traits'
else if ( UTF8traits::is6byte(*p) )
^
../../../dist/include/nsUTF8Utils.h:686:24: error: no member named
'supports_sse2' in namespace 'mozilla'
if (mozilla::supports_sse2())
~^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
gmake[5]: *** [nsUTF8UtilsSSE2.o] Error 1
gmake[5]: Leaving directory
`/usr/ports/www/firefox/work/mozilla-release/xpcom/string/src'
gmake[4]: *** [libs] Error 2
gmake[4]: Leaving directory
`/usr/ports/www/firefox/work/mozilla-release/xpcom/string'
gmake[3]: *** [libs] Error 2
gmake[3]: Leaving directory
`/usr/ports/www/firefox/work/mozilla-release/xpcom'
gmake[2]: *** [libs_tier_platform] Error 2
gmake[2]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release'
gmake[1]: *** 

Re: firefox 13.0,1 needs lang/gcc46 -- to RUN?!

2012-06-10 Thread Baptiste Daroussin
On Sat, Jun 09, 2012 at 08:27:11PM -0700, Doug Barton wrote:
 On 06/06/2012 12:18, Heino Tiedemann wrote:
  Hi,
  
  
  
  Why this ports needs his compiler to RUN?!
  
  
  firefox 13.0,1
 
 It's very common for binaries built with gcc to link to libgcc, and/or
 libstdc++:
 
 ldd firefox-bin  | grep gcc
   libstdc++.so.6 = /usr/local/lib/gcc46/libstdc++.so.6 (0x802b19000)
   libgcc_s.so.1 = /usr/local/lib/gcc46/libgcc_s.so.1 (0x8033a5000)
 
 In an ideal world, we would have separate packages for the runtime libs
 and the build tools so that packages could be more portable, but I would
 imagine that would be a lot of work.
 
 Doug

Yes that would be a lot of but it is the way we are doing. the upcoming stagedir
will open the door to easy package splitting and then allow easily to split gcc
into something like gcc-libs and gcc package or something like that.

regards,
Bapt


pgpgPjlR3EHvk.pgp
Description: PGP signature


Re: Imagemagick: FAIL, now in Magick++/demo/analyze.sh

2012-06-10 Thread Kevin Oberman
On Sun, Jun 10, 2012 at 9:19 AM, Kevin Oberman kob6...@gmail.com wrote:
 On Sat, Jun 9, 2012 at 8:02 PM, Doug Barton do...@freebsd.org wrote:
 The new version fails in a new location, even with the default options.


 Was this an amd64 system? All of my i386 systems installed the new
 ImageMagick cleanly, but my only amd64 system hit this.

Never mind. I just had an i386 system fail.
 --
 R. Kevin Oberman, Network Engineer
 E-mail: kob6...@gmail.com



-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.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: Imagemagick: FAIL, now in Magick++/demo/analyze.sh

2012-06-10 Thread Robert Huff

Rainer Hurling writes:

   The new version fails in a new location, even with the default options.
  
   Was this an amd64 system? All of my i386 systems installed the new
   ImageMagick cleanly, but my only amd64 system hit this.

  Yes, for me too, it fails on CURRENT amd64 system.

As of 20 minutes ago, ImageMagick-6.7.7.6 builds using clang
and default options), installs, and passes the internal test suite
on

FreeBSD 10.0-CURRENT #0: Sun Mar 11 08:20:02 EDT 2012  amd64 

I haven't tried to _use_ the program, but then I rarely do.

Respectfully,


Robert Huff


___
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


pkg_delete and +DEINSTALL

2012-06-10 Thread Andriy Gapon

While pkgng is growing momentum I have a small suggestion for outgoing pkg_* 
tools.
It seems that pkg_delete performs something like exec(+DEINSTALL, ...).
I think that it would be better to do exec(/bin/sh, +DEINSTALL, ...).
Rationale:
- no need to set x bit on +DEINSTALL
- no need to allow exec on /var/db filesystem
The problem is discovered by actually using noexec mount option.

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


WAS: Re: Why Are You NOT Using FreeBSD ? New: port annoyance LibreOffice

2012-06-10 Thread Robert Huff

O. Hartmann writes:

   Among all the default problems with ports, libreoffice[1] adds to the
   group of annoyances[2] at the moment. I don't know when I have seen
   portmaster -ad run through successfully last time. I need more and
   more -x options to exclude ports which fail to build.
  
   [1] german/libreoffice and libreoffice fails all the time in
   (LOCALIZED_LANG is set to de):

There is a known problem with libreoffice and boost,
specifically a conflict between the boost port and the internal
version.  There is a work-around; however, at the moment the
libreoffice maintainer does not have the time to rectify matters.
See the recent/ongoing thread in either ports@ or office@ for
more information.


Robert Huff

___
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: pkg_delete and +DEINSTALL

2012-06-10 Thread Chris Rees
On 10 June 2012 19:55, Andriy Gapon a...@freebsd.org wrote:

 While pkgng is growing momentum I have a small suggestion for outgoing pkg_* 
 tools.
 It seems that pkg_delete performs something like exec(+DEINSTALL, ...).
 I think that it would be better to do exec(/bin/sh, +DEINSTALL, ...).
 Rationale:
 - no need to set x bit on +DEINSTALL
 - no need to allow exec on /var/db filesystem
 The problem is discovered by actually using noexec mount option.

I don't think this is a bad idea, so I've copied in flz, the de-facto
pkg_install maintainer

 but don't forget that pkg_install is very close to death!

Chris
___
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: pkg_delete and +DEINSTALL

2012-06-10 Thread Florent Thoumie
On Sun, Jun 10, 2012 at 8:10 PM, Chris Rees cr...@freebsd.org wrote:
 On 10 June 2012 19:55, Andriy Gapon a...@freebsd.org wrote:

 While pkgng is growing momentum I have a small suggestion for outgoing pkg_* 
 tools.
 It seems that pkg_delete performs something like exec(+DEINSTALL, ...).
 I think that it would be better to do exec(/bin/sh, +DEINSTALL, ...).
 Rationale:
 - no need to set x bit on +DEINSTALL
 - no need to allow exec on /var/db filesystem
 The problem is discovered by actually using noexec mount option.

 I don't think this is a bad idea, so I've copied in flz, the de-facto
 pkg_install maintainer

  but don't forget that pkg_install is very close to death!

Aye. I've just handed my src commit bit for safekeeping but if you're
willing to put in the work, the plan sounds good assuming all scripts
have been rewritten in shell (for those that weren't already).

-- 
Florent Thoumie
f...@freebsd.org
FreeBSD Committer
___
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: pkg_delete and +DEINSTALL

2012-06-10 Thread Chris Rees
On 10 June 2012 20:46, Florent Thoumie f...@freebsd.org wrote:
 On Sun, Jun 10, 2012 at 8:10 PM, Chris Rees cr...@freebsd.org wrote:
 On 10 June 2012 19:55, Andriy Gapon a...@freebsd.org wrote:

 While pkgng is growing momentum I have a small suggestion for outgoing 
 pkg_* tools.
 It seems that pkg_delete performs something like exec(+DEINSTALL, ...).
 I think that it would be better to do exec(/bin/sh, +DEINSTALL, ...).
 Rationale:
 - no need to set x bit on +DEINSTALL
 - no need to allow exec on /var/db filesystem
 The problem is discovered by actually using noexec mount option.

 I don't think this is a bad idea, so I've copied in flz, the de-facto
 pkg_install maintainer

  but don't forget that pkg_install is very close to death!

 Aye. I've just handed my src commit bit for safekeeping but if you're
 willing to put in the work, the plan sounds good assuming all scripts
 have been rewritten in shell (for those that weren't already).

Good point-- I think I nuked the last remaining csh ones, but there
might be a few... Be sure to grep the ports tree first!

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


port unmaintained since 2005? drop it? misc/gpt*

2012-06-10 Thread Michael Scheidell
Two unmaintained ports, nothing depends on them, and upstream has not 
updated source since 2004, ftp server unresponsive.


http://www.freebsd.org/cgi/cvsweb.cgi/ports/misc/gpt31/Makefile
(gpt32: misc/gpt also unmaintained since 2005.

http://www.freebsd.org/cgi/cvsweb.cgi/ports/misc/gpt/Makefile
ftp server mentioned doesn't respond (ftp.freebsd.org has distfile),
upstream unmaintained since 2004, and upstream points to a different 
distfile (with different checksum and same version number), mentions an 
alpha version 4.0.


nothing depends on this (it is to install 'globus'), which I don't see 
in ports.


ps for misc/gpt has different errors, make -- -  7.4 i386, one on 9.0 
amd64 (did I say unmaintained port? ) I don't think anyone has attempted 
to use this since 4.x days.
any objection to me marking these deprecated unless someone steps up to 
maintain them?
(Mel: looks like you tried to offer submitter a fix, but I think this is 
a lost cause)

jan 21 pr: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164355

--
Michael Scheidell, CTO
*| * SECNAP Network Security Corporation
d: +1.561.948.2259
w: http://people.freebsd.org/~scheidell
___
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


NOPORTDOCS and NOPORTEXAMPLES

2012-06-10 Thread Warren Block
So references to NOPORTDOCS should be replaced with references to 
PORT_OPTIONS:MDOCS now?  Why that but not NOPORTEXAMPLES?

___
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


Retro-actively adjust port's deinstall operations?

2012-06-10 Thread Adam Strohl

Hello,

I've just submitted a PR to update the CouchDB port from 1.1.0 to 1.2.0:
http://www.freebsd.org/cgi/query-pr.cgi?pr=168923

Background: CouchDB's local.ini file stores all overridden options and 
default.ini the defaults, similar to /etc/rc.conf  /etc/defaults/rc.conf.


While updating the port I discovered that the existing port lists 
local.ini directly in pkg-plist instead of installing a local.ini.sample 
file and doing proper comparisons/tests for changes.  So it blindly 
removes this file on deinstall.


If my diff in the above PR is accepted when people uninstall the 
existing 1.1.0 port it will remove their config file.  The new port will 
see that there is no local.ini and copy in the sample for them but this 
is really awful for obvious reasons.


Is there a way to reach people with a warning about this _before_ they 
uninstall/reinstall so they can back up the file before upgrading?


Or is /usr/ports/UPDATING it? (and do I need to do anything special to 
have this listed there?)


P.S.
Any other feedback on the PR/diff is welcome.

--
Adam Strohl
http://www.ateamsystems.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: port unmaintained since 2005? drop it? misc/gpt*

2012-06-10 Thread Michael Scheidell



On 6/10/12 4:10 PM, Michael Scheidell wrote:
Two unmaintained ports, nothing depends on them, and upstream has not 
updated source since 2004, ftp server unresponsive.


http://www.freebsd.org/cgi/cvsweb.cgi/ports/misc/gpt31/Makefile
(gpt32: misc/gpt also unmaintained since 2005.

http://www.freebsd.org/cgi/cvsweb.cgi/ports/misc/gpt/Makefile
ftp server mentioned doesn't respond (ftp.freebsd.org has distfile),
upstream unmaintained since 2004, and upstream points to a different 
distfile (with different checksum and same version number), mentions 
an alpha version 4.0.


nothing depends on this (it is to install 'globus'), which I don't see 
in ports.



and, in fact:

grep globus /usr/ports/MOVED
net/globus4||2008-12-07|Has expired: Has been broken for more than 6 months


--
Michael Scheidell, CTO
*| * SECNAP Network Security Corporation
d: +1.561.948.2259
w: http://people.freebsd.org/~scheidell
___
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: Retro-actively adjust port's deinstall operations?

2012-06-10 Thread Chris Rees
On 10 June 2012 21:18, Adam Strohl adams-free...@ateamsystems.com wrote:
 Hello,

 I've just submitted a PR to update the CouchDB port from 1.1.0 to 1.2.0:
 http://www.freebsd.org/cgi/query-pr.cgi?pr=168923

 Background: CouchDB's local.ini file stores all overridden options and
 default.ini the defaults, similar to /etc/rc.conf  /etc/defaults/rc.conf.

 While updating the port I discovered that the existing port lists local.ini
 directly in pkg-plist instead of installing a local.ini.sample file and
 doing proper comparisons/tests for changes.  So it blindly removes this file
 on deinstall.

 If my diff in the above PR is accepted when people uninstall the existing
 1.1.0 port it will remove their config file.  The new port will see that
 there is no local.ini and copy in the sample for them but this is really
 awful for obvious reasons.

 Is there a way to reach people with a warning about this _before_ they
 uninstall/reinstall so they can back up the file before upgrading?

 Or is /usr/ports/UPDATING it? (and do I need to do anything special to have
 this listed there?)

I'm sorry, you're rather stuffed there.  The same happened with a port
I took over a while ago.

Actually if the older version doesn't install a .sample file (as it
doesn't), you could put a big warning in for it:

.include bsd.port.pre.mk

.if exists(${PREFIX}/whateverconfigfile) 
!exists(${PREFIX}/whateverconfigfile.sample)
IGNORE=  Please see UPDATING note {date}
.endif

Stick a note in UPDATING (perhaps like 20110815), and send a HEADSUP to ports@:

BEFORE you deinstall couchdb, make sure you take a backup of
default.ini, because the port will clobber it.

I've grabbed your PR and will investigate tomorrow.

Chris
___
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: NOPORTDOCS and NOPORTEXAMPLES

2012-06-10 Thread Jason Helfman
 So references to NOPORTDOCS should be replaced with references to
 PORT_OPTIONS:MDOCS now?  Why that but not NOPORTEXAMPLES?

You can use PORT_OPTIONS:MEXAMPLES for this case.

I believe I did this recently in www/flot

-jgh


___
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: Retro-actively adjust port's deinstall operations?

2012-06-10 Thread Bryan Drewery
On 6/10/2012 4:27 PM, Adam Strohl wrote:
 Where/when would this trigger?

This could block the upgrade as soon as they try to build it if they
already have the ini and do not have a sample file.

Regards,
Bryan Drewery

___
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: Retro-actively adjust port's deinstall operations?

2012-06-10 Thread Adam Strohl

On 6/11/2012 4:30, Bryan Drewery wrote:

On 6/10/2012 4:27 PM, Adam Strohl wrote:

Where/when would this trigger?


This could block the upgrade as soon as they try to build it if they
already have the ini and do not have a sample file.


The issue is that most things (ie; people or portupgrade) do a deinstall 
first, then a reinstall.  By the time the Makefile gets called for 
reinstall its too late and in my testing everything is ignored for 
deinstall because it uses the package's archived actions.


Or would this somehow hook on make deinstall too?
--
Adam Strohl
http://www.ateamsystems.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: Retro-actively adjust port's deinstall operations?

2012-06-10 Thread Bryan Drewery
On 6/10/2012 4:32 PM, Adam Strohl wrote:
 On 6/11/2012 4:30, Bryan Drewery wrote:
 On 6/10/2012 4:27 PM, Adam Strohl wrote:
 Where/when would this trigger?

 This could block the upgrade as soon as they try to build it if they
 already have the ini and do not have a sample file.
 
 The issue is that most things (ie; people or portupgrade) do a deinstall
 first, then a reinstall.  By the time the Makefile gets called for
 reinstall its too late and in my testing everything is ignored for
 deinstall because it uses the package's archived actions.
 
 Or would this somehow hook on make deinstall too?

portupgrade builds the port first, then deinstalls and installs.

So I think crees' suggestion will work.

Not sure about portmaster, but I imagine it would do the same, as it
could take *hours* to build and you would be left without the port in
the meantime.

Regards,
Bryan Drewery

___
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: Retro-actively adjust port's deinstall operations?

2012-06-10 Thread Adam Strohl

On 6/11/2012 4:36, Bryan Drewery wrote:

portupgrade builds the port first, then deinstalls and installs.

 So I think crees' suggestion will work.

Ah yes, that's right!  It only deinstalls after a successful build! 
Excellent.



Not sure about portmaster, but I imagine it would do the same, as it
could take *hours* to build and you would be left without the port in
the meantime.


Good call.

--
Adam Strohl
http://www.ateamsystems.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: NOPORTDOCS and NOPORTEXAMPLES

2012-06-10 Thread Warren Block

On Sun, 10 Jun 2012, Jason Helfman wrote:


So references to NOPORTDOCS should be replaced with references to
PORT_OPTIONS:MDOCS now?  Why that but not NOPORTEXAMPLES?


You can use PORT_OPTIONS:MEXAMPLES for this case.

I believe I did this recently in www/flot


But only after bsd.port.options.mk is included.  Here's what I was 
trying to do:


.if ${PORT_OPTIONS:MDOCS}
OPTIONS_DEFINE+=REFDOCS
REFDOCS_DESC=   Install the reference documents
OPTIONS_DEFAULT+=   REFDOCS
.endif

.if ${PORT_OPTIONS:MEXAMPLES}
OPTIONS_DEFINE+=EXAMPLES
EXAMPLES_DESC=  Install the example code
OPTIONS_DEFAULT+=   EXAMPLES
.endif

.include bsd.port.options.mk

...which doesn't work because DOCS and EXAMPLES don't exist yet.
___
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: NOPORTDOCS and NOPORTEXAMPLES

2012-06-10 Thread Jason Helfman
 On Sun, 10 Jun 2012, Jason Helfman wrote:

 So references to NOPORTDOCS should be replaced with references to
 PORT_OPTIONS:MDOCS now?  Why that but not NOPORTEXAMPLES?

 You can use PORT_OPTIONS:MEXAMPLES for this case.

 I believe I did this recently in www/flot

 But only after bsd.port.options.mk is included.  Here's what I was
 trying to do:

 .if ${PORT_OPTIONS:MDOCS}
 OPTIONS_DEFINE+=REFDOCS
 REFDOCS_DESC=   Install the reference documents
 OPTIONS_DEFAULT+=   REFDOCS
 .endif

 .if ${PORT_OPTIONS:MEXAMPLES}
 OPTIONS_DEFINE+=EXAMPLES
 EXAMPLES_DESC=  Install the example code
 OPTIONS_DEFAULT+=   EXAMPLES
 .endif

 .include bsd.port.options.mk

 ...which doesn't work because DOCS and EXAMPLES don't exist yet.



True. I should've mentioned some updated documentation here regarding
options, if you didn't know about it already:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-options.html

If anything doesn't make sense please raise the issue, and possibly send
in a documentation patch if you have time. White space patch doesn't count
;)

-jgh


___
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: Imagemagick: FAIL, now in Magick++/demo/analyze.sh

2012-06-10 Thread Kevin Oberman
On Sun, Jun 10, 2012 at 11:40 AM, Robert Huff roberth...@rcn.com wrote:

 Rainer Hurling writes:

   The new version fails in a new location, even with the default options.
  
   Was this an amd64 system? All of my i386 systems installed the new
   ImageMagick cleanly, but my only amd64 system hit this.

  Yes, for me too, it fails on CURRENT amd64 system.

        As of 20 minutes ago, ImageMagick-6.7.7.6 builds using clang
 and default options), installs, and passes the internal test suite
 on

 FreeBSD 10.0-CURRENT #0: Sun Mar 11 08:20:02 EDT 2012  amd64

        I haven't tried to _use_ the program, but then I rarely do.

Don't know about others, but i am still using gcc.

In any case, this won't show up with defaults as the default is to NOT
run tests. Tests were disabled by default last October. the commit
message gave no reason for why.

Of course, this means Doug must be wrong about using defaults.
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.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: Imagemagick: FAIL, now in Magick++/demo/analyze.sh

2012-06-10 Thread Doug Barton
On 06/10/2012 17:32, Kevin Oberman wrote:
 Of course, this means Doug must be wrong about using defaults.

 or, it means that Doug did 'make rmconfig' followed by 'make
config' where I enabled only the tests. I thought that was obvious from
context, but I'm happy to clarify.

Meanwhile, yes, the system I built it on last night was a 10-current amd64.

Doug

-- 

This .signature sanitized for your protection


___
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 unmaintained since 2005? drop it? misc/gpt*

2012-06-10 Thread perryh
Michael Scheidell scheid...@freebsd.org wrote:

 Two unmaintained ports, nothing depends on them, and upstream has
 not updated source since 2004, ftp server unresponsive.

 http://www.freebsd.org/cgi/cvsweb.cgi/ports/misc/gpt31/Makefile
 (gpt32: misc/gpt also unmaintained since 2005.

 http://www.freebsd.org/cgi/cvsweb.cgi/ports/misc/gpt/Makefile
 ftp server mentioned doesn't respond (ftp.freebsd.org has distfile),
 upstream unmaintained since 2004, and upstream points to a different 
 distfile (with different checksum and same version number), mentions
 an alpha version 4.0.

These are originally from NCSA, but the website mentioned in
the pkg-descr (http://www.gridpackagingtools.org/) now seems to
be promoting some kind of diet/nutritional approach.  The only
connection to middleware that immediately comes to mind is that
such sites tend to be frequented by those concerned about excessive
weight around their middle :)

Dunno what (if anything) they are currently good for, but it seems
that, at a minimum, the PORTVERSION and/or MASTER_SITES -- and the
pkg-descr -- need to be updated.
___
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: Imagemagick: FAIL, now in Magick++/demo/analyze.sh

2012-06-10 Thread Robert Huff

Kevin Oberman writes:

          As of 20 minutes ago, ImageMagick-6.7.7.6 builds using clang
   and default options), installs, and passes the internal test suite
   on

  In any case, this won't show up with defaults as the default is to NOT
  run tests. Tests were disabled by default last October. the commit
  message gave no reason for why.

I ran the tests using make test.  When I said defaults, I
_meant_ defaults.


Robert Huff
___
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 unmaintained since 2005? drop it? misc/gpt*

2012-06-10 Thread Robert Simmons
On Mon, Jun 11, 2012 at 4:31 AM,  per...@pluto.rain.com wrote:
 Michael Scheidell scheid...@freebsd.org wrote:

 Two unmaintained ports, nothing depends on them, and upstream has
 not updated source since 2004, ftp server unresponsive.

 http://www.freebsd.org/cgi/cvsweb.cgi/ports/misc/gpt31/Makefile
 (gpt32: misc/gpt also unmaintained since 2005.

 http://www.freebsd.org/cgi/cvsweb.cgi/ports/misc/gpt/Makefile
 ftp server mentioned doesn't respond (ftp.freebsd.org has distfile),
 upstream unmaintained since 2004, and upstream points to a different
 distfile (with different checksum and same version number), mentions
 an alpha version 4.0.

 These are originally from NCSA, but the website mentioned in
 the pkg-descr (http://www.gridpackagingtools.org/) now seems to
 be promoting some kind of diet/nutritional approach.  The only
 connection to middleware that immediately comes to mind is that
 such sites tend to be frequented by those concerned about excessive
 weight around their middle :)

 Dunno what (if anything) they are currently good for, but it seems
 that, at a minimum, the PORTVERSION and/or MASTER_SITES -- and the
 pkg-descr -- need to be updated.

I would have to think that that is a remnant of a project that is no
longer running.  The current owners of that domain are squatters:

Registrant ID:DOT-SY49XY2F9J0P
Registrant Name:Domain Admin
Registrant Organization:Maripon Management, Inc.
Registrant Street1:Office 2, 456-458 Strand
Registrant Street2:WC2R 0DZ
Registrant Street3:
Registrant City:London
Registrant State/Province:uk
Registrant Postal Code:n/a
Registrant Country:GB
Registrant Phone:+44.12053169373
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant Email:supp...@internet-guide.biz
___
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 unmaintained since 2005? drop it? misc/gpt*

2012-06-10 Thread b. f.
 On Mon, Jun 11, 2012 at 4:31 AM,  perryh at pluto.rain.com wrote:
  Michael Scheidell scheidell at freebsd.org wrote:
 
  Two unmaintained ports, nothing depends on them, and upstream has
  not updated source since 2004, ftp server unresponsive.
 
  http://www.freebsd.org/cgi/cvsweb.cgi/ports/misc/gpt31/Makefile
  (gpt32: misc/gpt also unmaintained since 2005.
 
  http://www.freebsd.org/cgi/cvsweb.cgi/ports/misc/gpt/Makefile
  ftp server mentioned doesn't respond (ftp.freebsd.org has distfile),
  upstream unmaintained since 2004, and upstream points to a different
  distfile (with different checksum and same version number), mentions
  an alpha version 4.0.
 
  These are originally from NCSA, but the website mentioned in
  the pkg-descr (http://www.gridpackagingtools.org/) now seems to
  be promoting some kind of diet/nutritional approach.  The only
  connection to middleware that immediately comes to mind is that
  such sites tend to be frequented by those concerned about excessive
  weight around their middle :)
 
  Dunno what (if anything) they are currently good for, but it seems
  that, at a minimum, the PORTVERSION and/or MASTER_SITES -- and the
  pkg-descr -- need to be updated.

 I would have to think that that is a remnant of a project that is no
 longer running.  The current owners of that domain are squatters:

The distribution files are at:

ftp://ftp.ncsa.uiuc.edu/aces/gpt/releases

and the homepage is:

http://grid.ncsa.illinois.edu/gpt/

(And Globus is at:

http://www.globus.org/toolkit/   )

Time to determine this:  1 min.

b.
___
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


ports need a uniq identifier, do you have any suggestion?

2012-06-10 Thread Baptiste Daroussin
Hi all,

In the ports tree we lack a unique identifier, while we could live without it
until now, it is more than needed for 2 upcoming features: pkgng and stage
directory support.

unique means something that will always be the same what ever the options are
and what ever the runtime they use are. But also means unique in term of in the
whole ports no other package will share its identifier.

currently the only equivalent of this in the ports tree is the origin of a
package, which will no more be unique with the upcoming sub package support
(coming along with stage directory) aka 1 origin to produce n package.

UNIQUENAME and LATEST_LINK fails in that area because they both can change
according to the runtime: py27- for example which will become py30- if you
change the default python.
LATEST_LINK by default also append the PKGNAMEPREFIX which some ports can be
really creative with.

should we introduce something new, should we fix one of the above? do you have
any suggestion?

regards,
Bapt


pgpBWquYtm9Gz.pgp
Description: PGP signature


Re: NOPORTDOCS and NOPORTEXAMPLES

2012-06-10 Thread Baptiste Daroussin
On Sun, Jun 10, 2012 at 06:05:49PM -0600, Warren Block wrote:
 On Sun, 10 Jun 2012, Jason Helfman wrote:
 
  So references to NOPORTDOCS should be replaced with references to
  PORT_OPTIONS:MDOCS now?  Why that but not NOPORTEXAMPLES?
 
  You can use PORT_OPTIONS:MEXAMPLES for this case.
 
  I believe I did this recently in www/flot
 
 But only after bsd.port.options.mk is included.  Here's what I was 
 trying to do:
 
 .if ${PORT_OPTIONS:MDOCS}
 OPTIONS_DEFINE+=REFDOCS
 REFDOCS_DESC=   Install the reference documents
 OPTIONS_DEFAULT+=   REFDOCS
 .endif
 
 .if ${PORT_OPTIONS:MEXAMPLES}
 OPTIONS_DEFINE+=EXAMPLES
 EXAMPLES_DESC=  Install the example code
 OPTIONS_DEFAULT+=   EXAMPLES
 .endif
 
 .include bsd.port.options.mk
 

Why not simply that way:

OPTIONS_DEFINE= ... DOCS EXAMPLES

DOCS_DESC=  Install the reference documents

And done.

Condtion an EXAMPLES on EXAMPLES options doesn't make sense to me.

by default DOCS and EXAMPLES are on expect if the user set NOPORTDOCS,
NOPORTEXAMPLES or OPTIONS_UNSET= DOCS EXAMPLES

regards,
Bapt


pgpK0ojeVXP2R.pgp
Description: PGP signature


libpng.so.6 missing

2012-06-10 Thread Waitman Gobble
Hi,

I was reading the handbook about burning DVD's and thought I would check out 
K3b as recommended... so I attempted to install from ports. After an hour or so 
of the make script building a whole bunch of stuff my patience wore out, and I 
bailed. 

ports tree csup this morning.

Now it seems many things that were working great will no longer load, it's 
missing libpng.so.6

# SciTE
Shared object libpng.so.6 not found, required by libpangocairo-1.0.so.0

# qtcreator
Shared object libpng.so.6 not found, required by libQtGui.so.4

# xxxterm
Shared object libpng.so.6 not found, required by libwebkitgtk-1.0.so.0


etc, etc. and so on.

Anyhow, i am not sure which package 'libpng.so.6' comes from.. anyone have a 
tip or a pointer?

these are installed..

# pkg_info | grep png
gstreamer-plugins-libpng-0.10.30,3 Gstreamer png plugin
png-1.5.10  Library for manipulating PNG images

# uname -a
FreeBSD hunny.waitman.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Sun Jun 10 
08:10:59 PDT 2012 root@:/usr/obj/usr/src/sys/KEYSHIA  amd64


Might be good to have a warning on the DVD page that attempting install of K3b 
can possibly dork up the entire system (?)

Thank you,

-- 
Waitman Gobble
San Jose California USA
___
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 unmaintained since 2005? drop it? misc/gpt*

2012-06-10 Thread Michael Scheidell



On 6/11/12 4:31 AM, per...@pluto.rain.com wrote:

Dunno what (if anything) they are currently good for, but it seems
that, at a minimum, the PORTVERSION and/or MASTER_SITES -- and the
pkg-descr -- need to be updated.

They still don't build.
And, they still aren't need by anything in ports tree (again, globus was 
deleted from ports tree in 2008)


anyone want to maintain them?  I'll tag your name on the ports for you.

--
Michael Scheidell, CTO
*| * SECNAP Network Security Corporation
d: +1.561.948.2259
w: http://people.freebsd.org/~scheidell
___
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: Documenting 'make config' options

2012-06-10 Thread Baptiste Daroussin
On Sun, Jun 10, 2012 at 01:00:05PM +0300, Vitaly Magerya wrote:
 Baptiste Daroussin b...@freebsd.org wrote:
  There was a PR[1] to use some dialog(1) feature to expose it to
  the user, would be nice if that extended description could
  implemented that way (using help button from dialog(1)) I do not
  plan to work on this now if someone want to do it that will be
  great
 
  1: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/123185
 
 I'm attaching a simple patch that allows you to hit F1 and view
 pkg-options-descr file in the options dialog (pkg- prefix
 should probably be removed, as that file has nothing to do with
 packages).

 --- bsd.port.mk.orig  2012-06-10 11:11:40.0 +0300
 +++ bsd.port.mk   2012-06-10 12:15:44.0 +0300
 @@ -2374,6 +2374,7 @@
  .endif
  
  DESCR?=  ${PKGDIR}/pkg-descr
 +OPTIONS_DESCR?=  ${PKGDIR}/pkg-options-descr
  PLIST?=  ${PKGDIR}/pkg-plist
  PKGINSTALL?= ${PKGDIR}/pkg-install
  PKGDEINSTALL?=   ${PKGDIR}/pkg-deinstall
 @@ -6068,8 +6069,15 @@
   (${ECHO_MSG} === Cannot create $${optionsdir}, check permissions; 
 exit 1)
  .endif
   @TMPOPTIONSFILE=$$(mktemp -t portoptions); \
 + if [ -e ${OPTIONS_DESCR} ]; then \
 + helpopt=--hfile ${OPTIONS_DESCR}; \
 + helptitle= (F1 for details); \
 + else \
 + helpopt=; \
 + helptitle=; \
 + fi; \
   trap ${RM} -f $${TMPOPTIONSFILE}; exit 1 1 2 3 5 10 13 15; \
 - ${DIALOG} --checklist Options for ${PKGNAME:C/-([^-]+)$/ \1/} 21 70 
 15 ${DEFOPTIONS} 2 $${TMPOPTIONSFILE} || { \
 + ${DIALOG} $${helpopt} --checklist Options for ${PKGNAME:C/-([^-]+)$/ 
 \1/}$${helptitle} 21 70 15 ${DEFOPTIONS} 2 $${TMPOPTIONSFILE} || { \
   ${RM} -f $${TMPOPTIONSFILE}; \
   ${ECHO_MSG} === Options unchanged; \
   exit 0; \

Besides I might change some naming here, (not much) this looks a really clever
way of bringing the features much more clever than what I could have been
thinking of. Thank you very much, I do some testing on it soon.

what I like is having a complete text to describe options, and not being 
limited to per option description.
On the change I'll just change OPTIONS_DESCR to OPTIONS_HELP and
pkg-options-descr to options-help

Thank you very much for the patch!

regards,
Bapt


pgp9jgipSER03.pgp
Description: PGP signature


Re: libpng.so.6 missing

2012-06-10 Thread Michael Scheidell



On 6/11/12 1:44 AM, Waitman Gobble wrote:

Hi,

I was reading the handbook about burning DVD's and thought I would check out 
K3b as recommended... so I attempted to install from ports. After an hour or so 
of the make script building a whole bunch of stuff my patience wore out, and I 
bailed.

ports tree csup this morning.

Now it seems many things that were working great will no longer load, it's 
missing libpng.so.6

# SciTE
Shared object libpng.so.6 not found, required by libpangocairo-1.0.so.0

# qtcreator
Shared object libpng.so.6 not found, required by libQtGui.so.4

# xxxterm
Shared object libpng.so.6 not found, required by libwebkitgtk-1.0.so.0


etc, etc. and so on.

Anyhow, i am not sure which package 'libpng.so.6' comes from.. anyone have a 
tip or a pointer?

something is still looking for an old version of png (libpng.so.6),  the 
new version of png uses lib: libpng.so.15.

Did you rebuild all packages from source?
quick 'cheat' would be to  restore libpng.so.6 to compat library from 
your backup, or another system.



--
Michael Scheidell, CTO
*| * SECNAP Network Security Corporation
d: +1.561.948.2259
w: http://people.freebsd.org/~scheidell
___
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: OPTIONSng and OPTIONS_SINGLE, OPTIONS_MULTI

2012-06-10 Thread Baptiste Daroussin
On Mon, Jun 11, 2012 at 06:49:35AM +0100, Matthew Seaman wrote:
 
 Dear all,
 
 In the new OPTIONS framework, we have some great new constructs for
 doing really useful stuff constraining what different combinations of
 options may be selected.
 
 One of these is OPTIONS_SINGLE which implements a 'radio button'
 permitting the choice of 1 item out of N options.  Well, actually, it
 allows choosing 1 out of N in its generic form.  Eg.
 
 OPTIONS_SINGLE=   EXAMPLE
 OPTIONS_SINGLE_EXAMPLE=   FOO BAR BAZ BLURFL
 
 (permits at exactly one out of FOO BAR BAZ BLURFL to be selected)
 
 Now, supposing the requirement is that 'at most one of those options'
 should be selected.  Currently that is done like this:
 
 OPTIONS_DEFINE= EXAMPLE
 OPTIONS_SINGLE=   EXAMPLE
 OPTIONS_SINGLE_EXAMPLE=   FOO BAR BAZ BLURFL
 
 (requires at most one of FOO BAR BAZ BLURFL to be selected)
 
 I find this unsatisfactory, partly for aesthetic reasons and partly
 because it doesn't make much sense to me.  Why should adding a normal
 on/off option with the same name as the SINGLE group mean you can choose
 either zero or one of these?  It might work if the way options were
 presented to the user was more sophisticated than dialog(1), so you
 could grey-out the SINGLE options when the controlling DEFINE is turned
 off, but dialog doesn't do that.
 
 Surely it is more sensible to say that OPTIONS_SINGLE is strictly
 'choose one from these options.'  Then you can implement 'zero or one of
 these options' by:
 
 OPTIONS_SINGLE= EXAMPLE
 OPTIONS_SINGLE_EXAMPLE=   FOO BAR BAZ BLURFL NONE_OF_THE_ABOVE
 
 Similar arguments apply to OPTIONS_MULTI.
 
 OPTIONS_MULTI= EXAMPLE2
 OPTIONS_MULTI_EXAMPLE2= QUX QUUX QUUUX
 
 means 'choose at one or more out of QUX QUUX QUUUX'  You can change that
 to mean 'choose any number out of QUX QUUX QUUUX' by:
 
 OPTIONS_DEFINE= EXAMPLE2
 OPTIONS_MULTI= EXAMPLE2
 OPTIONS_MULTI_EXAMPLE2= QUX QUUX QUUUX
 
 However, this is syntactically identical to just using normal on/off
 options with no constraints between them:
 
 OPTIONS_DEFINE= QUX QUUX QUUUX
 
 so that's just redundant.
 
 What do people think?
 
   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
 
 

I 100% agree on that, it should be quite easy to do just needs 2 new names :)

And a patch we shouldn't be complicated (while writting the patch be careful
than some ports are already using SINGLE the aesthetic way and need to be
patched at the same time.

regards,
Bapt


pgp4GEKTL3ZkU.pgp
Description: PGP signature