Re: [portupgrade] ArgumentError
Helmut Schneider wrote: # portupgrade -av --- Session started at: Mon, 15 Nov 2010 13:22:41 +0100 --- Skipping 'bsdpan-SNMP-Extension-PassPersist-0.03' because it is held by user (specify -f to force) --- Session ended at: Mon, 15 Nov 2010 13:23:19 +0100 (consumed 00:00:38) /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:953:in `initialize': ArgumentError (ArgumentError) from /usr/local/sbin/portupgrade:1004:in `new' from /usr/local/sbin/portupgrade:1004:in `do_upgrade' from /usr/local/sbin/portupgrade:814:in `main' from /usr/local/sbin/portupgrade:810:in `each' from /usr/local/sbin/portupgrade:810:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:791:in `initialize' from /usr/local/sbin/portupgrade:231:in `new' from /usr/local/sbin/portupgrade:231:in `main' from /usr/local/sbin/portupgrade:2219 # I recursively reinstalled portupgrade. Any further ideas? Seems the problem is caused by a(ny) bsdpan package. Unregistered it and now it succeeds. -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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
Duplicated origin: devel/gir-repository-libsoup - gir-repository-libsoup-0.6.5_4 gir-repository-libsoup-0.6.5_5
After a recent update, I have been receiving the following message when running pkgdb -Ffv Duplicated origin: devel/gir-repository-libsoup - gir-repository-libsoup-0.6.5_4 gir-repository-libsoup-0.6.5_5 Unregister any of them? [no] Apparently, I have two versions of the application installed: /var/db/pkg $ ll | grep -i libsoup drwxr-xr-x2 root wheel 512B 2010-11-23 05:53:41 EST gir-repository-libsoup-0.6.5_4/ drwxr-xr-x2 root wheel 512B 2010-11-23 08:23:09 EST gir-repository-libsoup-0.6.5_5/ drwxr-xr-x2 root wheel 512B 2010-11-23 05:53:26 EST libsoup-2.32.1/ drwxr-xr-x2 root wheel 512B 2010-11-23 05:53:33 EST libsoup-gnome-2.32.1/ I am unsure what specifically caused this to occur, The normal update went successfully and I believe I followed all of the procedures specified in the UPDATING file. I am assuming that I should just do a pkg_delete of the older version. Would that be correct. -- Jerry ✌ freebsd-ports.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: Duplicated origin: devel/gir-repository-libsoup - gir-repository-libsoup-0.6.5_4 gir-repository-libsoup-0.6.5_5
On Tue, 23 Nov 2010, Jerry wrote: After a recent update, I have been receiving the following message when running pkgdb -Ffv Duplicated origin: devel/gir-repository-libsoup - gir-repository-libsoup-0.6.5_4 gir-repository-libsoup-0.6.5_5 Unregister any of them? [no] Apparently, I have two versions of the application installed: /var/db/pkg $ ll | grep -i libsoup drwxr-xr-x2 root wheel 512B 2010-11-23 05:53:41 EST gir-repository-libsoup-0.6.5_4/ drwxr-xr-x2 root wheel 512B 2010-11-23 08:23:09 EST gir-repository-libsoup-0.6.5_5/ drwxr-xr-x2 root wheel 512B 2010-11-23 05:53:26 EST libsoup-2.32.1/ drwxr-xr-x2 root wheel 512B 2010-11-23 05:53:33 EST libsoup-gnome-2.32.1/ I am unsure what specifically caused this to occur, The normal update went successfully and I believe I followed all of the procedures specified in the UPDATING file. I am assuming that I should just do a pkg_delete of the older version. Would that be correct. /usr/ports/MOVED says: devel/gir-repository-libsoup|devel/libsoup|2010-11-20|merged into libsoup So you should be able to delete gir-repository-libsoup entirely. I did, and without any probl^$#...@*^%(NO CARRIER ___ 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: Forcing upgrade to latest AVAILABLE version of open office?
Here's what I need: a working, installable version of openoffice.org . The ports system on my FreeBSD 7.1 (which I need to keep stable for a few months) has only been willing to download a version that has security problems and will not build. The makefile version is 1.324 for openoffice.org-3 and 1.320 for openoffice.org-2 . I have issued a number of portupgrade commands, but portupgrade doesn't even seem to know of the existance of anything later, ... 1. Update your ports tree. 2. run portupgrade / portmaster to upgrade the ports in question. ... In section 4.5.1 two methods for getting ports are described: csup and portsnap. Yes, that is exactly what I need. I'll try it later when I have the chance, after I back up the whole ports area. And while the information is there, I find the documentation on freeBSD, and all recent open-source systems, to be disappointing. Maybe I can't get it into my head; maybe I can't get my head into it. But I feel that there is something missing. It's not something that I could provide simply by starting to write or rewrite the documentation; it's a shared understanding of what is needed: of the SEE ALSO that you need in man pages, of the need for architectonic summaries of things like the ports architecture, of the balance between structure and detail. If there's a place for me to contribute to -that- pool of skill, please let me know. Thanks. I'll let you know how this ports exercise goes for me. Mark Terribile ___ 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
ImageMagick upgrade problem
Puzzled I have perl installed with threads but getting the following upgrade problem with graphics/ImageMagick. The upgrade fails to recognise reality - Perl is installed with threads! with OpenEXR or OpenMP I get the same problem: dns1# make === ImageMagick-6.6.5.10 OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with threads or undefine WITH_IMAGEMAGICK_PERL. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. dns1# make === ImageMagick-6.6.5.10 OpenMP requires threads. Perl is non-threaded. Reinstall Perl with threads or undefine WITH_IMAGEMAGICK_PERL. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. dns1# pkg_info |grep perl p5-Error-0.17016Perl module to provide Error/exception support for perl: Er p5-Term-ReadKey-2.30 A perl5 module for simple terminal control p5-Test-Harness-3.22 Run perl standard test scripts with statistics p5-Time-HiRes-1.9721,1 A perl5 module implementing High resolution time, sleep, an p5-Tk-804.029 A re-port of a perl5 interface to Tk8.4 perl-threaded-5.8.9_4 Practical Extraction and Report Language postfix-policyd-spf-perl-2.007 SPF policy service for Postfix written in Perl ruby18-perl-0.2.9 A Ruby extension module to use the functions of Perl from R tmake-1.7_5 Extremely portable perl-based make utility Photographic Artist Permanent Installations Design Creative Imagery and Advanced Digital Techniques High Dynamic Range Photography Official Portraiture Combined darkroom digital creations Systems Adminstrator for the vizion2000.net network ___ 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 upgrade problem
Em Ter, 2010-11-23 às 17:50 +, David Southwell escreveu: Puzzled I have perl installed with threads but getting the following upgrade problem with graphics/ImageMagick. The upgrade fails to recognise reality - Perl is installed with threads! with OpenEXR or OpenMP I get the same problem: Make sure that perl is compiled with threads and. for me I solved the problem by defining in /etc/make.conf.PERL_THREADED=true it works, but the real solution is to fix the port either in IMagemagick or in perl ... ___ 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/152484: Build error of GTK-2.22.1_1
Synopsis: Build error of GTK-2.22.1_1 Responsible-Changed-From-To: freebsd-i386-freebsd-ports Responsible-Changed-By: arundel Responsible-Changed-When: Tue Nov 23 19:15:02 UTC 2010 Responsible-Changed-Why: This doesn't sound i386 specific. http://www.freebsd.org/cgi/query-pr.cgi?pr=152484 ___ 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
gir-repository entries in MOVED
My portmaster update today notified me that I had some of these ports on my system, relevant to the following entries in MOVED: devel/gir-repository-gconf2|devel/gconf2|2010-11-20|merged into gconf2 x11-fm/gir-repository-nautilus|x11-fm/nautilus|2010-11-20|merged into nautilus devel/gir-repository-libsoup|devel/libsoup|2010-11-20|merged into libsoup x11-toolkits/gir-repository-gtksourceview2|x11-toolkits/gtksourceview2|2010-11-20|merged into gtksourceview2 security/gir-repository-gnome-keyring||2010-11-20|Not buildable devel/gir-repository-dbus|devel/gobject-introspection|2010-11-20|merged into gobject-introspection Using portmaster or portupgrade the -o option is the way to fix this. Does this issue deserve an UPDATING entry? Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PR's not being picked up (Was Re: becoming a port committor)
Here is a patch to take care of removing of updating. On Mon, Nov 22, 2010 at 02:08:02PM -0800, Charlie Kester thus spake: On Mon 22 Nov 2010 at 11:28:36 PST Greg Byshenk wrote: I'm not a porter, but how about the below...? HTH -greg --- begin diff --- --- porting-submitting.html 2007-09-11 01:11:07.0 +0200 +++ porting-submitting.html 2010-11-22 20:14:54.0 +0100 @@ -69,6 +69,14 @@ /blockquote /div +div class=NOTE +blockquote class=NOTE +pbNote2:/b The instructions above are for creating a i class=EMPHASISnew/i +port. Port i class=EMPHASISupdates/i should be diff files instead of shar files, +as described in a href=port-upgrading.htmlUpgrading/a./p +/blockquote +/div + pOne more time, span class=emphasisi class=EMPHASISdo not include the original source distfile, the tt class=FILENAMEwork/tt directory, or the package you built with tt class=COMMANDmake package/tt/i/span./p --- end diff --- While we're at it, remove any mention of port updates from the existing note: --- begin diff --- --- porting-submitting.html.orig2010-11-22 14:01:35.0 -0800 +++ porting-submitting.html 2010-11-22 14:02:09.0 -0800 @@ -66,9 +66,8 @@ blockquote class=NOTE pbNote:/b You can make our work a lot easier, if you use a good description in the synopsis of the problem report. We prefer something like ``New port: -lt;categorygt;/lt;portnamegt; lt;short description of the portgt;'' for new ports -and ``Update port: lt;categorygt;/lt;portnamegt; lt;short description of the -updategt;'' for port updates. If you stick to this scheme, the chance that someone will +lt;categorygt;/lt;portnamegt; lt;short description of the portgt;'' for new ports. +If you stick to this scheme, the chance that someone will take a look at your PR soon is much better./p /blockquote /div --- end diff --- I'm not sure, but I suspect that this note has been the source of the confusion. ___ 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 -- -jgh --- porters-handbook/book.sgml 2010-11-23 11:49:21.0 -0800 +++ porters-handbook/book.sgml 2010-11-23 11:50:28.0 -0800 @@ -394,9 +394,7 @@ description in the synopsis of the problem report. We prefer something like quoteNew port: lt;categorygt;/lt;portnamegt; - lt;short description of the portgt;/quote for new ports and - quoteUpdate port: lt;categorygt;/lt;portnamegt; - lt;short description of the updategt;/quote for port updates. + lt;short description of the portgt;/quote. If you stick to this scheme, the chance that someone will take a look at your PR soon is much better./para /note ___ 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: gir-repository entries in MOVED
On Tue, 23 Nov 2010, Doug Barton wrote: My portmaster update today notified me that I had some of these ports on my system, relevant to the following entries in MOVED: devel/gir-repository-gconf2|devel/gconf2|2010-11-20|merged into gconf2 x11-fm/gir-repository-nautilus|x11-fm/nautilus|2010-11-20|merged into nautilus devel/gir-repository-libsoup|devel/libsoup|2010-11-20|merged into libsoup x11-toolkits/gir-repository-gtksourceview2|x11-toolkits/gtksourceview2|2010-11-20|merged into gtksourceview2 security/gir-repository-gnome-keyring||2010-11-20|Not buildable devel/gir-repository-dbus|devel/gobject-introspection|2010-11-20|merged into gobject-introspection Using portmaster or portupgrade the -o option is the way to fix this. Does this issue deserve an UPDATING entry? Given that it takes some looking otherwise, I'd say yes. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Suggestions on getting compiz working?
On 11/22/2010 07:24, Alexey Shuvaev wrote: Mmm... Error messages, back traces, etc.? I think, you know, doesn't work would not bring you much :) True, but I was hoping that someone had a working configuration and that they could send me some of the magic smoke. :) I'll try again with the new version and post a more complete report. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ImageMagick upgrade problem
Em Ter, 2010-11-23 Ã s 17:50 +, David Southwell escreveu: Puzzled I have perl installed with threads but getting the following upgrade problem with graphics/ImageMagick. The upgrade fails to recognise reality - Perl is installed with threads! with OpenEXR or OpenMP I get the same problem: Make sure that perl is compiled with threads and. for me I solved the problem by defining in /etc/make.conf.PERL_THREADED=true it works, but the real solution is to fix the port either in IMagemagick or in perl ... Just 'make PERL_THREADED=true' is probably easier, but the port is clearly broken. The logic is very oddly set out, but it relies on the value of PERL_THREADED which neither the Makefile nor any of the .Mk files defines. I assume that there was supposed to be some test of whether perl supports threading that never quite made it. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ 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: Forcing upgrade to latest AVAILABLE version of open office?
On Tue, Nov 23, 2010 at 4:35 PM, Mark Terribile materrib...@yahoo.comwrote: Here's what I need: a working, installable version of openoffice.org . The ports system on my FreeBSD 7.1 (which I need to keep stable for a few months) has only been willing to download a version that has security problems and will not build. The makefile version is 1.324 for openoffice.org-3 and 1.320 for openoffice.org-2 . I have issued a number of portupgrade commands, but portupgrade doesn't even seem to know of the existance of anything later, ... 1. Update your ports tree. 2. run portupgrade / portmaster to upgrade the ports in question. ... In section 4.5.1 two methods for getting ports are described: csup and portsnap. Yes, that is exactly what I need. I'll try it later when I have the chance, after I back up the whole ports area. And while the information is there, I find the documentation on freeBSD, and all recent open-source systems, to be disappointing. Maybe I can't Well, it is user written, and it is only as good as what we (the users and developers) have managed to put into it. That being said, I find that FreeBSD documentation is among the better for the open source projects that I am familiar with. There is a chapter in the FAQ about available documentation: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/support.html perhaps that will help you find what you need. get it into my head; maybe I can't get my head into it. But I feel that there is something missing. It's not something that I could provide simply by starting to write or rewrite the documentation; it's a shared understanding of what is needed: of the SEE ALSO that you need in man pages, of the need for architectonic summaries of things like the ports architecture, of the balance between structure and detail. Well, people are different from each other, in the way they think about what's logical, easy and so on (IMHO). Therefore, it isn't easy to say what's missing or what could be improved, unless you are able to put it into words. For myself, when I started with FreeBSD many years ago (FreeBSD 3.x), I had work experience from some SysV based unix systems. I had tried Linux, but it felt strange and different. When I tried FreeBSD, I was at home again immediately; all the commands were in their usual place, most of the config files were located where I expected them. And almost all commands had a man page. And the Project had a Handbook, both online and locally installed! Oh, those where the days... Well, enough of that. If there's a place for me to contribute to -that- pool of skill, please let me know. Well, if you have specific suggestions in mind, the documentation Project would be the place: http://www.freebsd.org/docproj/ Other intereting ports-related this (just in case you aren't aware of them): FreshPorts: http://www.freshports.org/ the port named portdowngrade HTH -- Regards, Torfinn ___ 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 upgrade problem
Em Ter, 2010-11-23 Ã s 17:50 +, David Southwell escreveu: Puzzled I have perl installed with threads but getting the following upgrade problem with graphics/ImageMagick. The upgrade fails to recognise reality - Perl is installed with threads! with OpenEXR or OpenMP I get the same problem: Make sure that perl is compiled with threads and. for me I solved the problem by defining in /etc/make.conf.PERL_THREADED=true it works, but the real solution is to fix the port either in IMagemagick or in perl ... Just 'make PERL_THREADED=true' is probably easier, but the port is clearly broken. The logic is very oddly set out, but it relies on the value of PERL_THREADED which neither the Makefile nor any of the .Mk files defines. I assume that there was supposed to be some test of whether perl supports threading that never quite made it. Tried the /etc/make.conf PERL_THREADED=true but still get the same result in graphics/ImageMagick: dns1# make clean === Cleaning for perl-threaded-5.8.9_4 === Cleaning for ImageMagick-6.6.5.10 dns1# make === ImageMagick-6.6.5.10 OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with threads or undefine WITH_IMAGEMAGICK_PERL. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. Photographic Artist Permanent Installations Design Creative Imagery and Advanced Digital Techniques High Dynamic Range Photography Official Portraiture Combined darkroom digital creations Systems Adminstrator for the vizion2000.net network ___ 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 upgrade problem
From: David Southwell da...@vizion2000.net Date: Tue, 23 Nov 2010 22:15:58 + Em Ter, 2010-11-23 Ã s 17:50 +, David Southwell escreveu: Puzzled I have perl installed with threads but getting the following upgrade problem with graphics/ImageMagick. The upgrade fails to recognise reality - Perl is installed with threads! with OpenEXR or OpenMP I get the same problem: Make sure that perl is compiled with threads and. for me I solved the problem by defining in /etc/make.conf.PERL_THREADED=true it works, but the real solution is to fix the port either in IMagemagick or in perl ... Just 'make PERL_THREADED=true' is probably easier, but the port is clearly broken. The logic is very oddly set out, but it relies on the value of PERL_THREADED which neither the Makefile nor any of the .Mk files defines. I assume that there was supposed to be some test of whether perl supports threading that never quite made it. Tried the /etc/make.conf PERL_THREADED=true but still get the same result in graphics/ImageMagick: dns1# make clean === Cleaning for perl-threaded-5.8.9_4 === Cleaning for ImageMagick-6.6.5.10 dns1# make === ImageMagick-6.6.5.10 OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with threads or undefine WITH_IMAGEMAGICK_PERL. *** Error code 1 I don't know why it is happening, but /etc/make.conf did not help. I had to define it on the command lines: $ make PERL_THREADED=true $ make deinstall PERL_THREADED=true $ make reinstall PERL_THREADED=true This worked fine, but I don't see why it is different from putting it in /etc/make.conf. Then again, I am way way far from being a make(1) expert. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ 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 upgrade problem
On Tue, 2010-11-23 at 13:19:49 -0800, Kevin Oberman wrote: Just 'make PERL_THREADED=true' is probably easier, but the port is clearly broken. The logic is very oddly set out, but it relies on the value of PERL_THREADED which neither the Makefile nor any of the .Mk files defines. I assume that there was supposed to be some test of whether perl supports threading that never quite made it. Yes, the port needs to check whether Perl is installed with threads and accordingly define PERL_THREADED. This is also being discussed on cvs-ports[1] and hopefully a fix will soon be committed. [1] http://lists.freebsd.org/pipermail/cvs-ports/2010-November/206982.html -- Sahil Tandon sa...@freebsd.org ___ 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 upgrade problem
I just committed a fix that a) worked for me, and b) I think is fairly robust, and even a candidate for being the right thing to do. Please give it a try, and let us know if it does or does not work for you. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Renaming a shared library in the port-framework to match FreeBSD naming schemes?
On Tue, Nov 23, 2010 at 03:42, O. Hartmann ohart...@mail.zedat.fu-berlin.de wrote: On 11/23/10 02:14, Andrew W. Nosenko wrote: On Mon, Nov 22, 2010 at 22:20, O. Hartmann ohart...@mail.zedat.fu-berlin.de wrote: But there lives another problem: Xerces people doesn't expect parallel installation of the evelopment part of Xerces-C (headers, pkg-config, etc). At least it seems so by listing the libxerces-c package from Ubuntu. I guess so, but some ports of the FreeBSD ports (i.e. textproc/xalan-c) want xerces-c2 (which is 2.7.0). I try build xalan-c with the new xerces-c3 and see if it can handle the new header and libraries. I see three variants: (1) simple: just mark these ports (c2 and c3) as conflicting, ... in my testcase I did. And, for my personal taste, it is the best option. Be close to upstream as much as possible, IMHO, is the best way. (2) semi-simple: split each xerces-c port at the two: run-time and development. Runtime contains a shered library, development contains anything other. Mark development parts as conflictitng. ... well, in such a case we converge much to the weird Linux mess, I guess. (3) move each port away from each other's way: move headers into own versioned deirectory (e.g. from include/xercesc/ to insclude/xercesc-3.1/xercesc/), drop libxerces-c.so (if any -- I don't know), rename pkg-config (.pc) file, and static library (if any), may be something yet another, like documentation -- need to look at the actual install. All these changes hidden from the users through pkg-config's .pc, therefore only one problem for developers will be changed (non-standard name of the .pc file, i.e. pkg-config's module). ... this would bring up other complications for ports expecting libs and headers at places where the solo installation normally resides. But ATM I see no better way to allow parallel installation of the packages that aren't intended for parallel installation by theirs authors... I tend to install it as a unique port with conflicts activated. Hope there are no further conflicts other than xalan-c. And I have some feelings that either existing xalan-c able to compile against current xerces-c or there is newer version that able. -- Andrew W. Nosenko andrew.w.nose...@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: multimedia/vlc Compile failure on upgrade
On 11/22/2010 15:50, David Southwell wrote: I have added jsa@ to the cc list. Which got filtered into my folder for the ports@ mailing list, which I seldom read. A good way to notify a maintainer to an issue is to file a problem report via send-pr or on the web. http://www.freebsd.org/send-pr.html Someone did file a report, along with a patch which seems to address the issue. The patch has already been committed. ___ 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
net-im/prosody needs new maintainer!
Hi, I want the net-im/prosody port updated but I have no time to work on it. So, I need to hand it off to someone else. If you would like to take over maintaining it please let me know. Thanks, Kelly ___ 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
