Re: Adding licensing info to my ports: some questions
Hi, On Wed, Jan 18, 2012 at 12:13 AM, Doug Barton do...@freebsd.org wrote: On 01/17/2012 14:35, Torfinn Ingolfsen wrote: Anything can go wrong, but it is (IMO) quite easy to state the intention of the FreeBSD Project in this case. You're making the very common mistake of assuming that the law has anything to do with reality. It doesn't. The fact that we're making claims about legal issues opens the project up to a wide array of hairy liability problems. It doesn't matter how baseless the lawsuit is, sometimes just filing the suit creates enough damage to kill the thing sued. No, I'm aware that in some parts of the world, law practice is far away from the intention of the law. Luckily, it isn't that bad all over the world, not yet anyway. However, I think that anyone who tries to _do_ something should have the courage / balls / whatever to stand up and try to make the best he or she can, with the means available. Otherwise, we could all just go and hide under a stone, and nothing would be done. Now, can we get back to our regular schedule, please? -- Regards, Torfinn Ingolfsen ___ 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: Adding licensing info to my ports: some questions
Nikola Lečić wrote: Anyway, it wasn't clear from the bsd.licenses.mk that we should use 'multi' in situations of 'any later version'. This means that all licensing info of eg. GPL2+ ports must be updated when GPL4 appears... No, we should not use this. Not just because of the potential of having to check and correct every port when GPLv4 appears. In my book, licenced under GPLv2 or GPLv3 is something fundamentally different from licenced under GPLv2 or any later version. The licence framework should be able to make this distinction. Another issue is that the licence infrastructure seems to be making statements about the licence of an application, while the committers only tend to look at individual source packages. What would be the licence of an application whose source is published under BSD licence, but that is linked with both GPv3 and OpenSSL-libraries? I tend to agree with Doug and others that it is probably better to scrap the entire idea. Making assertions about licences and what is accepted is a hairy field, best left to experts. Regards, Johan pgpqnD8hLmBzH.pgp Description: PGP signature
Re: xcb-util
I found two broken rebuild after upgrade xcb: 1) vlc doesn't build ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) 2) kalzium doesn't build ( It is corrected after force rebuild something from ocaml\* or facile\*) ___ 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: xcb-util
Subbsd sub...@gmail.com wrote: I found two broken rebuild after upgrade xcb: 1) vlc doesn't build ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) 2) kalzium doesn't build ( It is corrected after force rebuild something from ocaml\* or facile\*) 3) xfce4-wm libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' g Heino ___ 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: xcb-util
On Wednesday 18 January 2012 03:07:09 you wrote: I found two broken rebuild after upgrade xcb: 1) vlc doesn't build ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) 2) kalzium doesn't build ( It is corrected after force rebuild something from ocaml\* or facile\*) I use mplayer and I don't have a problem. Is kalzium part of kdeedu? If it is than I didn't have a problem to rebuilt. 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
Correcting problems disclosed by pkg_libchk
On another thread I noticed a reference to pkg_libchk. I was interested in seeing what it would disclose on my system, so I ran it. pkg_libchk -Rrv It produced a great deal of output. This is one section dealing with Firefox firefox-9.0.1,1: located: /usr/local/lib/firefox/components/libbrowsercomps.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/components/libdbusservice.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/components/libmozgnome.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/firefox-bin misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/libsoftokn3.so misses libmozsqlite3.so found at /usr/local/lib/firefox/libmozsqlite3.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/libxpcom.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/libxul.so misses libmozsqlite3.so found at /usr/local/lib/firefox/libmozsqlite3.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/libxul.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/plugin-container misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/sdk/lib/libxpcom.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/sdk/lib/libxul.so misses libmozsqlite3.so found at /usr/local/lib/firefox/libmozsqlite3.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/sdk/lib/libxul.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. If I am reading this correctly, the libmozalloc.so library is missing. I have tried doing a forced re-install of Firefox, but the same condition exists. Other packages have several libraries apparently missing also. Since re-installing the port does not seem to alleviate the problem, what is the prescribed method of correcting it? Thanks! -- Carmel carmel...@hotmail.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: xcb-util
Subbsd wrote: I found two broken rebuild after upgrade xcb: 1) vlc doesn't build ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) 2) kalzium doesn't build ( It is corrected after force rebuild something from ocaml\* or facile\*) pkg_libchk from sysutils/bsdadminscripts would point you to all ports that should be rebuilt. -- Sphinx of black quartz judge my vow. ___ 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: Upgrading libs with many dependent ports
Kevin Oberman wrote: I have just been cleaning up the mess caused by the upgrade of xcb-utils. On my systmes I have hundreds of ports that will be re-built by the methods listed in UPDATING, even though the vast majority of them are only dependent on other ports that are dependent on xcb-utils, but don't actually load any of the libraries in xcb-utils. It is a huge waste of time and CPU cycles. I think that I can see two ways of eliminating the rebuilding of ports that don't need it. One is rather manual but can be done now while the other wou;d be automatic, but would need to be written by someone who is far better at writing shell scripts than I. The manual method would be to install sysutils/bsdadminscripts and use a command like `pkg_libchk | grep -E xcb-.+.so | sort tmpfile` to provide a list of ports that actually are linked to the libraries in question. This would be fed into portmaster to rebuild just these ports. (I guess I could use awk and uniq to remove repeats.) Should this become a preferred method of handling this problem? You can use pkg_libchk -oc to have it report rather port name and skip status junk. You don't need uniq, use sort -u. Anyway portmaster will uniq them anyway. -- Sphinx of black quartz judge my vow. ___ 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
CFT: sudo 1.8.4b5 update
I've got a patch to update sudo to the latest 1.8.4 beta (b5) available at [1]. There's lots of changes in this release and I want to give people who run more complex sudo installs than I do a chance to test it out. I'd appreciate people running this update and reporting back with either success or failure stories, so I feel better about eventually committing the update once it is out of beta. [1]: http://people.freebsd.org/~wxs/sudo-beta.diff -- WXS ___ 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: sudo 1.8.4b5 update
On Wed, Jan 18, 2012 at 10:28:33AM -0500, Wesley Shields wrote: I've got a patch to update sudo to the latest 1.8.4 beta (b5) available at [1]. There's lots of changes in this release and I want to give people who run more complex sudo installs than I do a chance to test it out. I'd appreciate people running this update and reporting back with either success or failure stories, so I feel better about eventually committing the update once it is out of beta. [1]: http://people.freebsd.org/~wxs/sudo-beta.diff I forgot to mention that the changes are all documented at: http://www.sudo.ws/sudo/devel.html#1.8.4b5 Please at least take a look through there if you run an even moderately complex sudo environment. -- WXS ___ 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: sudo 1.8.4b5 update
Wesley Shields wrote on 18.01.2012 19:28: I've got a patch to update sudo to the latest 1.8.4 beta (b5) available at [1]. There's lots of changes in this release and I want to give people who run more complex sudo installs than I do a chance to test it out. I'd appreciate people running this update and reporting back with either success or failure stories, so I feel better about eventually committing the update once it is out of beta. [1]: http://people.freebsd.org/~wxs/sudo-beta.diff -- WXS Hi, Wesley. Dunno if this is complicated scheme enought, but i'm hold my sudoers in ldap directory (via sudo.schema for OpenLDAP). All working fine to me with this version of sudo. Thanks. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: irc/bitlbee skype support
Hi Lyubomir, On Jan 16, 2012, at 08:14, Lyubomir Grigorov wrote: I do not currently have any plans for a irc/bitlbee-devel port - I simply do not have the time to maintain it. Sorry. Skype protocol is included by default in 3.0.4. I don't think the port builds it (and thus PC-BSD PBI also doesn't include it). All the source and scripts are there. Brix, can you confirm this? I couldn't find the skype protocol or the skyped python script if I build Bitlbee 3.0.4 from ports. That is correct. As noted in my commit message for 3.0.4: Skype protocol support will be available at a later point in time, as it has few external dependencies not currently available in ports. Regards, Brix -- Henrik Brix Andersen ___ 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
Encoding question
Hi, I'm trying to compile a C++ software on FreeBSD. While compiling, this error shows up: error: stray '\357' in program error: stray '\273' in program error: stray '\277' in program This file is reported (by file[1]) to be UTF-8 Unicode (with BOM) C program text, with CRLF line terminators while the rest of the files in the package are ASCII C program text, with CRLF line terminators. While I can convert the file with iconv -c -f utf-8 -t ascii file new_file in the post extract stage, I wonder if there is a more suitable way for achieving the same thing. Also I would like to avoid this software from depending on iconv. Thanks in advance. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Update mail/assp port
On 2012-01-18 12:36, Good ol' boy wrote: I wanted to try using ASSP with my Postfix installation. Apparently, the older single threaded version is the one available in the ports system. Are there any plans to either update it to ASSP V2 or add it as a new port? Thanks! I don't have any plans to make a port for assp version 2 since version 1 works for me. ASSP version 2 is very easy to install without a port and has an auto-update feature. Some people have asked about the port but no one has moved forward with that very much. Let me know if this is something you want to pursue and I can give you what I had started from a year ago and what has to be done to do things right. Rusty ___ 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
Update mail/assp port
I wanted to try using ASSP with my Postfix installation. Apparently, the older single threaded version is the one available in the ports system. Are there any plans to either update it to ASSP V2 or add it as a new port? Thanks! ___ 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: MASTER_SITE_FEDORA_LINUX in bsd.sites.mk
On 17 Jan 2012 08:32, per...@pluto.rain.com wrote: Jason Helfman j...@freebsd.org wrote: I was looking at update bsd.sites.mk, and found that MASTER_SITE_FEDORA_LINUX is only used in one port. Any objection to moving this site-index into x11-themes/bluecurve-themes, and removing from bsd.sites.mk? There is also a referrence to it in bsd.linux-rpm.mk, but not certain how this should be handled. This seems to be a legacy site-index. This might better be asked on ports@ (Cc'd). I would think that Fedora is a sufficiently common distribution to warrant keeping this setting in a central location, in case of future need in a non-X port, unless its presence is causing problems. I worry about the ethics of 'stealing' Fedora's bandwidth with other people's ports; we should only be using their mirrors if it's explicitly developed by Fedora. 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: Adding licensing info to my ports: some questions
On 01/18/2012 04:34, Johan van Selst wrote: Nikola Lečić wrote: Anyway, it wasn't clear from the bsd.licenses.mk that we should use 'multi' in situations of 'any later version'. This means that all licensing info of eg. GPL2+ ports must be updated when GPL4 appears... No, we should not use this. Not just because of the potential of having to check and correct every port when GPLv4 appears. In my book, licenced under GPLv2 or GPLv3 is something fundamentally different from licenced under GPLv2 or any later version. The licence framework should be able to make this distinction. Another issue is that the licence infrastructure seems to be making statements about the licence of an application, while the committers only tend to look at individual source packages. What would be the licence of an application whose source is published under BSD licence, but that is linked with both GPv3 and OpenSSL-libraries? I tend to agree with Doug and others that it is probably better to scrap the entire idea. Making assertions about licences and what is accepted is a hairy field, best left to experts. I hope this effort is not completely abandoned since it does seem to offer an easy way to get a general sense of the license status of a system, jail or vm. What about a more explicitly passive approach that does not make assertions about an application's overall license (c.f. linking issues) or the user's acceptance but just makes such license files as do exist easier to find? If such a simple license tracking feature is useful (even if not suitable for management, compliance, budgeting, license acceptance and the like) then something that would grab the locations of license documents in a port's source files and copies the relevant files into a default license location /usr/local/share/licenses/port/ would be enough. Would this ports knob feature (LICENSE_=) disappear if the project were scrapped? I doubt this simpler approach would be ITIL compliant ;) but since that is not a goal and the bulk of anything to do with licenses involves lawyers anyway, the ports/pkg system should probably try to do as little as possible regarding claims and interpretation. Surely keeping copies of licenses in an easy to find location doesn't equate to making any legal claim ? NB: I am not a lawyer :) cheers, ps: ls -1 /usr/local/share/licenses/*/LICENSE | wc -l 221 ls -1 /usr/local/share/licenses/*/* | grep -E MIT|BSD |wc -l 86 ls -1 /usr/local/share/licenses/*/* | grep -E LGPL*|GPL* |wc -l 116 Of course, the above system has 1200 ports installed so there's a ways to go before one could say tracking was happening :) ___ 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: MASTER_SITE_FEDORA_LINUX in bsd.sites.mk
--On January 18, 2012 9:09:10 PM + Chris Rees utis...@gmail.com wrote: I worry about the ethics of 'stealing' Fedora's bandwidth with other people's ports; we should only be using their mirrors if it's explicitly developed by Fedora. I'm not sure I follow. If Fedora is making an rpm available for download, how is it stealing their bandwidth to download the rpm from there? Wouldn't be equally stealing to download it from anywhere else? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: MASTER_SITE_FEDORA_LINUX in bsd.sites.mk
On Wed, Jan 18, 2012 at 09:09:10PM +, Chris Rees wrote: I worry about the ethics of 'stealing' Fedora's bandwidth with other people's ports; we should only be using their mirrors if it's explicitly developed by Fedora. Correct. dougb has pointed this out before and no one has taken the cycles to go act on it. Consider this a task that needs volunteers. (A similiar caveat applies to the Debian and NetBSD sites; I believe it was Debian he flagged previously.) mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Correcting problems disclosed by pkg_libchk
On Wed, Jan 18, 2012 at 5:02 AM, Carmel carmel...@hotmail.com wrote: On another thread I noticed a reference to pkg_libchk. I was interested in seeing what it would disclose on my system, so I ran it. pkg_libchk -Rrv It produced a great deal of output. This is one section dealing with Firefox firefox-9.0.1,1: located: /usr/local/lib/firefox/components/libbrowsercomps.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/components/libdbusservice.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/components/libmozgnome.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/firefox-bin misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/libsoftokn3.so misses libmozsqlite3.so found at /usr/local/lib/firefox/libmozsqlite3.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/libxpcom.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/libxul.so misses libmozsqlite3.so found at /usr/local/lib/firefox/libmozsqlite3.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/libxul.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/plugin-container misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/sdk/lib/libxpcom.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/sdk/lib/libxul.so misses libmozsqlite3.so found at /usr/local/lib/firefox/libmozsqlite3.so. firefox-9.0.1,1: located: /usr/local/lib/firefox/sdk/lib/libxul.so misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. If I am reading this correctly, the libmozalloc.so library is missing. I have tried doing a forced re-install of Firefox, but the same condition exists. Other packages have several libraries apparently missing also. Since re-installing the port does not seem to alleviate the problem, what is the prescribed method of correcting it? Thanks! No, it is telling you that the files listed seem to miss the libraries re[ported, but that they were found in /usr/local/lib/firefox. Firefox does its own thing for finding its sharable libs, so /usr/local/lib/firefox is not in the loader hint, but firefox knows where they are and does load them. this is a side effect of -v. You asked for false positives and you got them. Oh, and specifying -R or -r is only relevant when a specific port is listed. 'pkg_libchk -Rrv' does nothing more than just 'pkg_libchk -v'. -- 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: Upgrading libs with many dependent ports
On Tue, Jan 17, 2012 at 06:43:27PM -0800 I heard the voice of Kevin Oberman, and lo! it spake thus: Take a look at pkg_chklib. It is quite optimized and runs multiple checks in parallel so that you can run it on 1100 ports in about 1.5 minutes. I've looked at it. From the samples and docs I've seen, it seems to do both more and less than I want. That's not a knock on it, it just goes in a slightly different direction than I want. -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
On Wednesday 18 January 2012 08:28:38 Volodymyr Kostyrko wrote: Subbsd wrote: I found two broken rebuild after upgrade xcb: 1) vlc doesn't build ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) 2) kalzium doesn't build ( It is corrected after force rebuild something from ocaml\* or facile\*) pkg_libchk from sysutils/bsdadminscripts would point you to all ports that should be rebuilt. I ran pkg_libchk and I got: diablo-jdk-16 misses libz.so.4 diablo-jre-16 misses libz.so.4 and both misses liodbcinst.so but I have: ocate libz.so.4 /usr/local/lib/compat/libz.so.4 but I don't have libodbcinst.so and I rebuilt diablo. libreoffice 3.4.5 misses libjawt.so I have: locate libjawt.so /usr/local/diablo-jdk1.6.0/jre/lib/i386/libjawt.so /usr/local/diablo-jre1.6.0/lib/i386/libjawt.so redland and rasqar misses libyajl.so.1 which I don't have and opera -11.60 misses libz.so.5 which I don't have. Which ports have libs which I need it, please? 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
with the cvs history? trying to help INDEX builds.
in manually trying to build an index for a tinderbox/binary/portmaster
distribution, I started to look at some of the things that slow these down.
and, being a former real-time, robotics guy... I figure, take ONE line
of code out, and you make things faster.
anyway, worth the cycles?
take out -.include bsd.port.pre.mk; -.if ${ARCH} == sparc64
-BROKEN=Does not install on sparc64
-.endif
and replace it with NOT_FOR_ARCHS=sparc64 ?
without bsd.port.PRE, you won't (try) to pull in lots of other things,
optional things (options,perl, mysql, etc)
worth the cvs history cycles to do this?
cvs diff: Diffing .
Index: Makefile
===
RCS file: /home/pcvs/ports/games/xarchon/Makefile,v
retrieving revision 1.16
diff -u -r1.16 Makefile
--- Makefile10 Aug 2011 09:01:56 -1.16
+++ Makefile19 Jan 2012 01:27:56 -
@@ -29,10 +29,6 @@
@${REINPLACE_CMD} -e 's|Xarchon_Evolution::||' \
${WRKSRC}/src/Xarchon_Genetic.hpp
-.include bsd.port.pre.mk
+NOT_FOR_ARCHS=sparc64
-.if ${ARCH} == sparc64
-BROKEN=Does not install on sparc64
-.endif
-
-.include bsd.port.post.mk
+.include bsd.port.mk
cvs diff: Diffing files
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
___
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: xcb-util
On Wed, Jan 18, 2012 at 05:46:07PM -0600, ajtiM wrote: On Wednesday 18 January 2012 08:28:38 Volodymyr Kostyrko wrote: Subbsd wrote: I found two broken rebuild after upgrade xcb: pkg_libchk from sysutils/bsdadminscripts would point you to all ports that should be rebuilt. I ran pkg_libchk and I got: diablo-jdk-16 misses libz.so.4 Unrelated to the issue... FYI the above package provides what the below package is utilized for. diablo-jre-16 misses libz.so.4 and both misses liodbcinst.so ___ 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: xcb-util
On Wed, Jan 18, 2012 at 6:08 PM, Jason Hellenthal jh...@dataix.net wrote: On Wed, Jan 18, 2012 at 05:46:07PM -0600, ajtiM wrote: On Wednesday 18 January 2012 08:28:38 Volodymyr Kostyrko wrote: Subbsd wrote: I found two broken rebuild after upgrade xcb: pkg_libchk from sysutils/bsdadminscripts would point you to all ports that should be rebuilt. I ran pkg_libchk and I got: diablo-jdk-16 misses libz.so.4 Unrelated to the issue... FYI the above package provides what the below package is utilized for. diablo-jre-16 misses libz.so.4 and both misses liodbcinst.so FYI The man page for pkg_libchk discusses this and explains that thy are false positives. pkg_libchk -o | grep xcb- should just give the relevant information. -- 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
