RE: FreeBSD Port: dovecot-1.2.14
Hi I was just wondering if there is a port for dovecot 2 in the works already or if I could be any assistance in getting it up and running? Check out these URL's http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/150789 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/150790 This is no guaranty that it will work, you could however start testing. Regards, Johan Hendriks ___ 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: LICENSE_FILE=${WRKSRC}/LICENSE
ash...@freebsd.org (Ashish SHUKLA) writes:
Anonymous writes:
ash...@freebsd.org (Ashish SHUKLA) writes:
Anonymous writes:
ash...@freebsd.org (Ashish SHUKLA) writes:
[1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/146513
Why do you need to copy license file in post-extract?
I added because specifying '${WRKSRC}/LICENSE' as 'LICENSE_FILE' results
in
a conflict because License infrastructure in ports system also creates a
file
named LICENSE. So, I'm just copying it to some name other than LICENSE,
and
than mentioning that in the LICENSE_FILE.
Ah, so you're referring to _LICENSE_REPORT that's created in_LICENSE_DIR.
It's not just the case of a single license file named `LICENSE' but
multiple
licenses with same filename but in different directories are affected as
well.
Does the following diff fixes it for you?
Yes, the following diff works fine and I don't have to rename LICENSE file
anymore.
[...]
I've filed ports/148808 for the sweeping change so it's not forgotten
after 8.1-RELEASE is out.
Great :)
Since that PR is committed can you remove workarounds then?
%%
diff --git a/cad/qelectrotech/Makefile b/cad/qelectrotech/Makefile
index 33f3d26..8a69682 100644
--- a/cad/qelectrotech/Makefile
+++ b/cad/qelectrotech/Makefile
@@ -20,15 +20,12 @@ QT_COMPONENTS= gui network svg xml \
INSTALLS_ICONS=yes
LICENSE= GPLv2
-LICENSE_FILE= ${WRKSRC}/COPYING
+LICENSE_FILE= ${WRKSRC}/LICENSE
MAN1= qelectrotech.1
MANLANG=es fr.ISO8859-1 fr.UTF-8 fr pt_PT
MANCOMPRESSED= yes
-post-extract:
- @${CP} ${WRKSRC}/LICENSE ${WRKSRC}/COPYING
-
do-configure:
${MV} ${WRKSRC}/man/files/pt ${WRKSRC}/man/files/pt_PT
${REINPLACE_CMD} -e 's,/usr/local/,${PREFIX}/,g' \
diff --git a/irc/irssi-otr/Makefile b/irc/irssi-otr/Makefile
index 8f013e1..5f675a0 100644
--- a/irc/irssi-otr/Makefile
+++ b/irc/irssi-otr/Makefile
@@ -21,6 +21,9 @@ LIB_DEPENDS= otr.4:${PORTSDIR}/security/libotr \
gcrypt.17:${PORTSDIR}/security/libgcrypt
RUN_DEPENDS= irssi:${PORTSDIR}/irc/irssi
+LICENSE= GPLv2
+LICENSE_FILE= ${WRKSRC}/LICENSE
+
USE_CMAKE= yes
USE_LDCONFIG= yes
USE_GNOME= glib20
diff --git a/multimedia/libvpx/Makefile b/multimedia/libvpx/Makefile
index 74cebf0..c68090a 100644
--- a/multimedia/libvpx/Makefile
+++ b/multimedia/libvpx/Makefile
@@ -25,7 +25,7 @@ USE_LDCONFIG= yes
MAKE_JOBS_SAFE=yes
LICENSE= BSD
-LICENSE_FILE= ${WRKSRC}/COPYING
+LICENSE_FILE= ${WRKSRC}/LICENSE
OPTIONS= DEBUG Enable debugging OFF \
POSTPROCEnable postprocessing ON \
@@ -74,9 +74,6 @@ CONFIGURE_ARGS+= --target=ia64-linux-gcc
IGNORE=no support for ${ARCH} the moment. testing/patches are welcome
.endif
-post-extract:
- @${MV} ${WRKSRC}/LICENSE ${WRKSRC}/COPYING
-
post-patch:
@${GREP} -Rl '^#!/bin/bash' ${WRKSRC} |${XARGS} ${REINPLACE_CMD} \
-e 's,#!/bin/bash,#!${LOCALBASE}/bin/bash,g'
diff --git a/www/xpi-foxyproxy/Makefile b/www/xpi-foxyproxy/Makefile
index 8d4abaa..34d9c38 100644
--- a/www/xpi-foxyproxy/Makefile
+++ b/www/xpi-foxyproxy/Makefile
@@ -18,12 +18,10 @@ XPI_NUM=2464
XPI_ID=foxypr...@eric.h.jung
LICENSE= GPLv2
-LICENSE_FILE= ${WRKSRC}/COPYING
+LICENSE_FILE= ${WRKSRC}/LICENSE
xpi-post-extract:
@${FIND} ${WRKSRC} -type f -name '*.js' |${XARGS} ${SED} -i '' -e
's/[[:space:]]*$$//g'
- @${MV} ${WRKSRC}/LICENSE ${WRKSRC}/COPYING
- @${GREP} -Rl LICENSE ${WRKSRC} |${XARGS} ${REINPLACE_CMD} -e
s/LICENSE/COPYING/g
pre-install:
@${FIND} ${WRKSRC} -type f -name '*.orig' |${XARGS} ${RM} -f
diff --git a/www/xpi-foxyproxy/pkg-plist b/www/xpi-foxyproxy/pkg-plist
index 43e5867..6c7b668 100644
--- a/www/xpi-foxyproxy/pkg-plist
+++ b/www/xpi-foxyproxy/pkg-plist
@@ -1,4 +1,4 @@
-%%XPI_XPIDIR%%/COPYING
+%%XPI_XPIDIR%%/LICENSE
%%XPI_XPIDIR%%/chrome.manifest
%%XPI_XPIDIR%%/chrome/content/about.js
%%XPI_XPIDIR%%/chrome/content/about.xul
%%
___
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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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: LICENSE_FILE=${WRKSRC}/LICENSE
Anonymous swel...@gmail.com writes:
ash...@freebsd.org (Ashish SHUKLA) writes:
Anonymous swel...@gmail.com writes:
Why do you need to copy license file in post-extract?
I added because specifying '${WRKSRC}/LICENSE' as 'LICENSE_FILE' results in
a conflict because License infrastructure in ports system also creates a
file
named LICENSE. So, I'm just copying it to some name other than LICENSE, and
than mentioning that in the LICENSE_FILE.
I've filed ports/148808 for the sweeping change so it's not forgotten
after 8.1-RELEASE is out.
Since that PR is committed can you remove workarounds then?
A few more obvious workarounds this time by other committers (CC'd).
Renaming license files no longer has an effect, bsd.licenses.mk will
always install them under their respective names in _LICENSE_DIR to
avoid confusion/collision.
%%
diff --git a/devel/buildapp/Makefile b/devel/buildapp/Makefile
index fcb24e4..31e3dc5 100644
--- a/devel/buildapp/Makefile
+++ b/devel/buildapp/Makefile
@@ -19,7 +19,7 @@ BUILD_DEPENDS=sbcl:${PORTSDIR}/lang/sbcl
RUN_DEPENDS= ${BUILD_DEPENDS}
LICENSE= BSD
-LICENSE_FILE= ${WRKSRC}/doc/LICENSE-buildapp
+LICENSE_FILE= ${WRKSRC}/doc/LICENSE
PLIST_FILES= bin/buildapp
PORTDOCS= *
@@ -27,9 +27,6 @@ PORTDOCS= *
WRKSRC=${WRKDIR}/${DISTNAME}-${PORTVERSION}
ALL_TARGET=
-post-extract:
- @${MV} ${WRKSRC}/doc/LICENSE ${WRKSRC}/doc/LICENSE-buildapp
-
do-install:
@${INSTALL_PROGRAM} ${WRKSRC}/${PORTNAME} ${PREFIX}/bin/
diff --git a/graphics/openjpeg/Makefile b/graphics/openjpeg/Makefile
index 18f1495..7b96c20 100644
--- a/graphics/openjpeg/Makefile
+++ b/graphics/openjpeg/Makefile
@@ -21,7 +21,7 @@ COMMENT= An open-source JPEG 2000 codec
LIB_DEPENDS= tiff.4:${PORTSDIR}/graphics/tiff
LICENSE= BSD
-LICENSE_FILE= ${WRKSRC}/COPYRIGHT
+LICENSE_FILE= ${WRKSRC}/jp3d/LICENSE.txt
MAKE_JOBS_UNSAFE= yes
USE_GMAKE= yes
@@ -39,9 +39,6 @@ PLIST_FILES= include/openjpeg.h \
SHLIB_VER= 2
-post-extract:
- ${LN} ${WRKSRC}/jp3d/LICENSE.txt ${WRKSRC}/COPYRIGHT
-
post-patch:.SILENT
${FIND} ${WRKSRC} -type f -name Makefile -exec ${REINPLACE_CMD}
's|gcc|$$(CC)|g' {} +
diff --git a/mail/spamilter/Makefile b/mail/spamilter/Makefile
index 2ad28d2..a2aef9d 100644
--- a/mail/spamilter/Makefile
+++ b/mail/spamilter/Makefile
@@ -17,7 +17,7 @@ MAINTAINER= din...@freebsd.org
COMMENT= A Sendmail LibMilter filter to block spam
LICENSE= BSD
-LICENSE_FILE= ${WRKSRC}/COPYRIGHT
+LICENSE_FILE= ${WRKSRC}/LICENSE
HAS_CONFIGURE= yes
USE_RC_SUBR= spamilter.sh
@@ -67,9 +67,6 @@ PLIST_FILES+= bin/dnsblchk bin/dnsblupd bin/ipfwmtad
bin/mxlookup \
PORTDOCS= Changelog INSTALL LICENSE docs.html docs.txt db.rcpt \
db.rdnsbl db.sndr policy.html spamilter.rc
-post-extract:
- ${LN} ${WRKSRC}/LICENSE ${WRKSRC}/COPYRIGHT
-
pre-configure:
${REINPLACE_CMD} \
-e s=/etc/spamilter.rc=${PREFIX}/etc/spamilter.rc= \
diff --git a/math/stepulator/Makefile b/math/stepulator/Makefile
index a443e0c..6d505aa 100644
--- a/math/stepulator/Makefile
+++ b/math/stepulator/Makefile
@@ -18,7 +18,7 @@ MAINTAINER= din...@freebsd.org
COMMENT= Scientific calculator implementing RPN notation for GNUstep
LICENSE= BSD
-LICENSE_FILE= ${WRKSRC}/COPYRIGHT
+LICENSE_FILE= ${WRKSRC}/LICENSE
USE_GNUSTEP= yes
USE_GNUSTEP_BACK= yes
@@ -27,9 +27,6 @@ USE_GNUSTEP_INSTALL= yes
WRKSRC=${WRKDIR}/Stepulator-gs
-post-extract:
- ${LN} ${WRKSRC}/LICENSE ${WRKSRC}/COPYRIGHT
-
post-install:
${INSTALL_DATA} ${WRKSRC}/LICENSE \
${GNUSTEP_LOCAL_APPS}/Stepulator.app/Resources/
diff --git a/net/sixxs-aiccu/Makefile b/net/sixxs-aiccu/Makefile
index 8480a29..7662f7a 100644
--- a/net/sixxs-aiccu/Makefile
+++ b/net/sixxs-aiccu/Makefile
@@ -20,7 +20,7 @@ COMMENT= SixXS IPv6 TIC+ tunnel broker heartbeat client
LIB_DEPENDS= gnutls-openssl.40:${PORTSDIR}/security/gnutls
LICENSE= BSD
-LICENSE_FILE= ${WRKSRC}/COPYRIGHT
+LICENSE_FILE= ${WRKSRC}/doc/LICENSE
USE_RC_SUBR= sixxs-aiccu
USE_GMAKE= yes
@@ -32,9 +32,6 @@ WRKSRC= ${WRKDIR}/aiccu
BUILD_WRKSRC= ${WRKDIR}/aiccu/unix-console
PORTDOCS= README
-post-extract:
- ${CP} ${WRKSRC}/doc/LICENSE ${WRKSRC}/COPYRIGHT
-
post-patch:
@${REINPLACE_CMD} \
-e 's:verbose true:verbose false:' \
diff --git a/security/xyssl/Makefile b/security/xyssl/Makefile
index 3039459..f482ad3 100644
--- a/security/xyssl/Makefile
+++ b/security/xyssl/Makefile
@@ -16,16 +16,13 @@ MAINTAINER= po...@freebsd.org
COMMENT= A liteweight SSL and TLS toolkit for C developers
LICENSE= BSD
-LICENSE_FILE= ${WRKSRC}/COPYRIGHT
+LICENSE_FILE= ${WRKSRC}/BSD.txt
# HAS_CONFIGURE= no
# GNU_CONFIGURE= no
PORTDOCS= BSD.txt ChangeLog
-post-extract:
- ${LN}
Re: LICENSE_FILE=${WRKSRC}/LICENSE
Anonymous writes:
ash...@freebsd.org (Ashish SHUKLA) writes:
Anonymous writes:
ash...@freebsd.org (Ashish SHUKLA) writes:
Anonymous writes:
ash...@freebsd.org (Ashish SHUKLA) writes:
[1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/146513
Why do you need to copy license file in post-extract?
I added because specifying '${WRKSRC}/LICENSE' as 'LICENSE_FILE' results
in
a conflict because License infrastructure in ports system also creates a
file
named LICENSE. So, I'm just copying it to some name other than LICENSE,
and
than mentioning that in the LICENSE_FILE.
Ah, so you're referring to _LICENSE_REPORT that's created in_LICENSE_DIR.
It's not just the case of a single license file named `LICENSE' but
multiple
licenses with same filename but in different directories are affected as
well.
Does the following diff fixes it for you?
Yes, the following diff works fine and I don't have to rename LICENSE file
anymore.
[...]
I've filed ports/148808 for the sweeping change so it's not forgotten
after 8.1-RELEASE is out.
Great :)
Since that PR is committed can you remove workarounds then?
Thanks for the mention. I'll remove the workarounds.
--
Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0
freebsd.org!ashish | http://people.freebsd.org/~ashish/
Avoid Success At All Costs !!
pgp8NlpFtDP7V.pgp
Description: PGP signature
Re: FreeBSD Port: dovecot-1.2.14
Hi, On Tue, Sep 28, 2010 at 09:52:51AM +0200, Johan Hendriks wrote: I was just wondering if there is a port for dovecot 2 in the works already or if I could be any assistance in getting it up and running? Check out these URL's http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/150789 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/150790 This is no guaranty that it will work, you could however start testing. I am wondering whether there is an established convention about port names and versions since Dovecot 2.0 is now the newest stable branch. Will mail/dovecot be updated to 2.0 and 1.2 moved to mail/dovecot12 or will a new port be added for 2.0? -- Denny Lin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: dovecot-1.2.14
Postfix uses that standard anyways Denny. postfix is at 2.7 presently with postfix24, postfix25, etc being alternatives to track. On 28 Sep 2010, at 06:54, Denny Lin wrote: Hi, On Tue, Sep 28, 2010 at 09:52:51AM +0200, Johan Hendriks wrote: I was just wondering if there is a port for dovecot 2 in the works already or if I could be any assistance in getting it up and running? Check out these URL's http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/150789 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/150790 This is no guaranty that it will work, you could however start testing. I am wondering whether there is an established convention about port names and versions since Dovecot 2.0 is now the newest stable branch. Will mail/dovecot be updated to 2.0 and 1.2 moved to mail/dovecot12 or will a new port be added for 2.0? -- Denny Lin ___ 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
samba 3.5.5
Hi, wondering if someone is working on it, I need to make some local changes, and having a working freebsd version would be most welcome :-) (there's an openbsd) danny ___ 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
Request to include VMware X11 drivers on the installation media
[ As was recommended by Joel Dahl I am resending this request to the ports list as I haven't got response from freebsd-x11 maintainers. ] Hi, We (VMware) would like to stop shipping our mouse and graphics drivers for newer releases of X server as part of our VMware Tools distribution and instead rely on versions of said drivers shipping with guest OSes. Currently both xf86-input-vmmouse and xf86-video-vmware are part of the ports tree but it would be helpful for the users if they were also available on the installation media. Could you please tell me what is needed to move the drivers in question there? Thanks! -- Dmitry ___ 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: Request to include VMware X11 drivers on the installation media
on 28/09/2010 19:45 Dmitry Torokhov said the following: [ As was recommended by Joel Dahl I am resending this request to the ports list as I haven't got response from freebsd-x11 maintainers. ] Hi, We (VMware) would like to stop shipping our mouse and graphics drivers for newer releases of X server as part of our VMware Tools distribution and instead rely on versions of said drivers shipping with guest OSes. Currently both xf86-input-vmmouse and xf86-video-vmware are part of the ports tree but it would be helpful for the users if they were also available on the installation media. Could you please tell me what is needed to move the drivers in question there? Things like that are decided by FreeBSD Release Engineering team. I think that such a notice/request should be sent to them directly. -- 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
Idea: entries in UPDATING for each release
Right now, people who install ports from a -release CD and then start upgrading don't have a clear marker for how far back to go in UPDATING. A simple entry would be enough: 20100703: AFFECTS: AUTHOR: FreeBSD 8.1-RELEASE Not sure what AFFECTS should say. There might be other useful information that could be included in the note. Comments? ___ 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: Request to include VMware X11 drivers on the installation media
Hi, I just added FreeBSD Release Engineers r...@freebsd.org as vmware might not be aware of that address. - Reference: From: Andriy Gapon a...@freebsd.org Date: Tue, 28 Sep 2010 20:20:58 +0300 Message-id: 4ca223fa.3010...@freebsd.org Andriy Gapon wrote: on 28/09/2010 19:45 Dmitry Torokhov said the following: [ As was recommended by Joel Dahl I am resending this request to the ports list as I haven't got response from freebsd-x11 maintainers. ] Hi, We (VMware) would like to stop shipping our mouse and graphics drivers for newer releases of X server as part of our VMware Tools distribution and instead rely on versions of said drivers shipping with guest OSes. Currently both xf86-input-vmmouse and xf86-video-vmware are part of the ports tree but it would be helpful for the users if they were also available on the installation media. Could you please tell me what is needed to move the drivers in question there? Things like that are decided by FreeBSD Release Engineering team. I think that such a notice/request should be sent to them directly. -- 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 Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text; Not HTML, quoted-printable base 64 spam formats. Avoid top posting, It cripples itemised cumulative responses. ___ 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: Request to include VMware X11 drivers on the installation media
On Tuesday, September 28, 2010 11:11:43 am Julian H. Stacey wrote: Hi, I just added FreeBSD Release Engineers r...@freebsd.org as vmware might not be aware of that address. - Reference: From: Andriy Gapon a...@freebsd.org Date: Tue, 28 Sep 2010 20:20:58 +0300 Message-id: 4ca223fa.3010...@freebsd.org Andriy Gapon wrote: on 28/09/2010 19:45 Dmitry Torokhov said the following: [ As was recommended by Joel Dahl I am resending this request to the ports list as I haven't got response from freebsd-x11 maintainers. ] Hi, We (VMware) would like to stop shipping our mouse and graphics drivers for newer releases of X server as part of our VMware Tools distribution and instead rely on versions of said drivers shipping with guest OSes. Currently both xf86-input-vmmouse and xf86-video-vmware are part of the ports tree but it would be helpful for the users if they were also available on the installation media. Could you please tell me what is needed to move the drivers in question there? Things like that are decided by FreeBSD Release Engineering team. I think that such a notice/request should be sent to them directly. Thank you Julian and Andriy, I indeed was not aware of the proper address. -- Dmitry ___ 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
Broken net-im/ejabberd
Hi everyone, DON'T PANIC I'm the maintainer of net-im/ejabberd, which recently became broken due to my lack of synchronization with the upgrade of lang/erlang. Jimi Olgeni (maintainer of lang/erlang) has submitted a diff[1] containing the update, which I'll commit in a day or two. To try it yourself, do: host!user: ~ % cp -R /usr/ports/net-im/ejabberd . host!user: ~ % fetch -o - http://people.freebsd.org/~ashish/diffs/ejabberd.diff |patch host!user: ~ % make -C ejabberd build deinstall install clean Replace word install with package above, if you also like to build package of it. If you experience any issue with the diff, please report to me. References: [1] http://people.freebsd.org/~ashish/diffs/ejabberd.diff HTH -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 freebsd.org!ashish | http://people.freebsd.org/~ashish/ Avoid Success At All Costs !! pgpYaysD7iAhr.pgp Description: PGP signature
Using portmaster with different PYTHON_VERSION
Hello! I'm trying to install Python additional ports (e.g. www/py-httplib2) for different Python versions (2.6 and 3.1) in the same system using the portmaster. Those packages (py26-httplib2 vs py31-httplib2) do not conflict (they may be used simultaneously, don't overwrite each other's files etc.). But they have single origin, which seems to confuse the portmaster: PYTHON_VERSION=python2.6 portmaster www/py-httplib2 ... === Installation of www/py-httplib2 (py26-httplib2-0.6.0) complete Then PYTHON_VERSION=python3.1 portmaster www/py-httplib2 ... === Upgrade of py26-httplib2-0.6.0 to py31-httplib2-0.6.0 complete So portmaster thinks that it's an upgrade, and removes py26-httplib2, which is not correct - I want to keep both packages: py26-httplib2-0.6.0 A comprehensive HTTP client library py31-httplib2-0.6.0 A comprehensive HTTP client library Am I missing some portmaster's tunable, or it just doesn't support such ports yet? -- Sincerely, Dmitry nic-hdl: LYNX-RIPE ___ 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
FreeBSD Port: xf86-video-ati-6.13.0 update to 6.13.2?
Hi all, Xorg has released xf86-video-ati-6.13.2. http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/ With 6.13.0 my ati 4770 isn't working correct. I get graphical error in taskbar and menu from kde4 and fluxbox. I tested it with FreeBSD 8.1 and PC-BSD 8.1. Greetings ___ 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: Idea: entries in UPDATING for each release
On 9/28/10 2:07 PM, Warren Block wrote: Right now, people who install ports from a -release CD and then start upgrading don't have a clear marker for how far back to go in UPDATING. +1 A simple entry would be enough: 20100703: AFFECTS: AUTHOR: FreeBSD 8.1-RELEASE Not sure what AFFECTS should say. There might be other useful information that could be included in the note. Comments? Maybe the AFFECTS line can be left out completely, and just state FreeBSD X.Y-RELEASE. Regards, -- Glen Barber ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: net/isc-dhcp41-client, dhclient-script and DHCPv6
On Wed, Sep 22, 2010 at 06:20:07PM +1000, Lawrence Stewart wrote: Hi Wesley, I've been playing with DHCPv6 and in doing so, ran into an apparent problem with the net/isc-dhcp41-client port. I've switched to using the script provided by upstream. Thanks for noticing this and sorry for the delay in response. -- 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: Using portmaster with different PYTHON_VERSION
On 9/28/2010 11:30 AM, Dmitry Pryanishnikov wrote: Hello! I'm trying to install Python additional ports (e.g. www/py-httplib2) for different Python versions (2.6 and 3.1) in the same system using the portmaster. Those packages (py26-httplib2 vs py31-httplib2) do not conflict (they may be used simultaneously, don't overwrite each other's files etc.). But they have single origin, which seems to confuse the portmaster: PYTHON_VERSION=python2.6 portmaster www/py-httplib2 ... === Installation of www/py-httplib2 (py26-httplib2-0.6.0) complete Then PYTHON_VERSION=python3.1 portmaster www/py-httplib2 ... === Upgrade of py26-httplib2-0.6.0 to py31-httplib2-0.6.0 complete So portmaster thinks that it's an upgrade, and removes py26-httplib2, which is not correct - I want to keep both packages: py26-httplib2-0.6.0 A comprehensive HTTP client library py31-httplib2-0.6.0 A comprehensive HTTP client library Am I missing some portmaster's tunable, or it just doesn't support such ports yet? You're not missing anything. Portmaster's assumption is that $ORIGIN is always unique. I would also argue that there is a fundamental assumption in the ports infrastructure that what you're doing here (installing both versions on the same system) is not supported. The ability to make the version of things like python or perl variable is a great feature of the ports infrastructure, but my understanding has always been that this would be a system-wide option, and that installing different versions of the same language on the same system is not supported. That said, assuming that the 2 ports create different /var/db/pkg directories, and do not install files into the same location, you could use portmaster's -g option for the first install, then re-install the package after installing the second port. Or you could just not use portmaster for the second one. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!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: FreeBSD Port: xf86-video-ati-6.13.0 update to 6.13.2?
On Tue, Sep 28, 2010 at 2:48 PM, Lokadamus lokada...@gmx.de wrote: Hi all, Xorg has released xf86-video-ati-6.13.2. http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/ With 6.13.0 my ati 4770 isn't working correct. I get graphical error in taskbar and menu from kde4 and fluxbox. I tested it with FreeBSD 8.1 and PC-BSD 8.1. I would like to test this in PC-BSD 8.1 on a ATI raedon 3200 mobile card. right now 3d acceleration in KDE4 is disabled.. my hope is that this new driver will enable 3D. how would I test this in PC-BSD? -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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: net/isc-dhcp41-client, dhclient-script and DHCPv6
On 09/29/10 06:56, Wesley Shields wrote: On Wed, Sep 22, 2010 at 06:20:07PM +1000, Lawrence Stewart wrote: Hi Wesley, I've been playing with DHCPv6 and in doing so, ran into an apparent problem with the net/isc-dhcp41-client port. I've switched to using the script provided by upstream. Thanks for noticing this and sorry for the delay in response. No worries at all and thanks for looking into this. I appreciate it. Cheers, Lawrence ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Idea: entries in UPDATING for each release
On Tue, Sep 28, 2010 at 1:07 PM, Warren Block wbl...@wonkity.com wrote: Right now, people who install ports from a -release CD and then start upgrading don't have a clear marker for how far back to go in UPDATING. A simple entry would be enough: 20100703: AFFECTS: AUTHOR: FreeBSD 8.1-RELEASE Not sure what AFFECTS should say. There might be other useful information that could be included in the note. Comments? I like the idea, it would make looking that info up easier for anyone running anything other than the default GENERIC kernel. -- Adam Vande More ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: xf86-video-ati-6.13.0 update to 6.13.2?
On Tue, 28 Sep 2010, Sam Fourman Jr. wrote: On Tue, Sep 28, 2010 at 2:48 PM, Lokadamus lokada...@gmx.de wrote: Hi all, Xorg has released xf86-video-ati-6.13.2. http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/ With 6.13.0 my ati 4770 isn't working correct. I get graphical error in taskbar and menu from kde4 and fluxbox. I tested it with FreeBSD 8.1 and PC-BSD 8.1. I would like to test this in PC-BSD 8.1 on a ATI raedon 3200 mobile card. right now 3d acceleration in KDE4 is disabled.. my hope is that this new driver will enable 3D. how would I test this in PC-BSD? If PC-BSD doesn't have some special procedure for installing normal FreeBSD ports, and you're comfortable with modifying ports, copy the x11-drivers/xf86-video-ati port to a new directory, modify the Makefile to show PORTVERSION= 6.13.2, run make makesum to update the checksums, deinstall the old port and install the new one. This assumes there are lots of other things, including that there are no changes in pkg-plist. I've been running 6.13.2 since the announcement, no problems so far.___ 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: Idea: entries in UPDATING for each release
On Tue, Sep 28, 2010 at 12:07:08PM -0600, Warren Block wrote: Right now, people who install ports from a -release CD and then start upgrading don't have a clear marker for how far back to go in UPDATING. A simple entry would be enough: 20100703: AFFECTS: AUTHOR: FreeBSD 8.1-RELEASE Not sure what AFFECTS should say. There might be other useful information that could be included in the note. Comments? I'm certainly not opposed to the idea but what exactly do we use for a date? When the tree is tagged? When the release media is finalized and published to mirrors? What about tag slippage? Do we account for that? If the only goal is to get a rough idea of when a release was cut then either when the tree is tagged or when the media is pushed out to mirrors is probably sufficient. -- 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: Idea: entries in UPDATING for each release
On Tue, 28 Sep 2010, Wesley Shields wrote: On Tue, Sep 28, 2010 at 12:07:08PM -0600, Warren Block wrote: Right now, people who install ports from a -release CD and then start upgrading don't have a clear marker for how far back to go in UPDATING. A simple entry would be enough: 20100703: AFFECTS: AUTHOR: FreeBSD 8.1-RELEASE Not sure what AFFECTS should say. There might be other useful information that could be included in the note. Comments? I'm certainly not opposed to the idea but what exactly do we use for a date? When the tree is tagged? When the release media is finalized and published to mirrors? What about tag slippage? Do we account for that? It's probably not too critical as long as the note is before the post-release thaw and subsequent major updates. The existing UPDATING around the time of 8.1-RELEASE has entries for 20100626 and then 20100715. It was eleven days after 8.1-RELEASE that the next note was added, so at least for that example, timing isn't very tight. If the only goal is to get a rough idea of when a release was cut then either when the tree is tagged or when the media is pushed out to mirrors is probably sufficient. Sounds fine. ___ 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
