Re: gcc 4.2 update
On Fri, 10 Apr 2009 01:18:17 +0200 Marc Espie wrote: > I finally got time to update the gcc port to something more recent. > It no longer makes sense to use a snapshot in my opinion. > > I've rebuilt the adastrap stuff (not 100% I'm current built with > libc.so.50*) > > Since there are actual users of this gcc version, please tell me if > you see any issues. > > I'd like to know if any of the relevant arches no longer work. > > I'm aware there is related work going on, such as gcj-enabling work. > I expect these ports changes to be mostly unrelated... Patch applied cleanly. I'll test on i386, but still downloading; it will take awhile. When done, I'll see if it plays well with OpenOffice3. -- J.C. Roberts
Re: EPIC4 perl flavor
On 2009/04/10 21:11, James Wright wrote:
> Attached patch for EPIC4 adding a perl flavor which lets you run perl
> scripts. Also included is 'CFLAGS+= -O0' which fixes a problem (on
> i386 at least), where hitting ctl-C (to add colours), hangs EPIC. If
> the latter needs to stay in my private tree until a better solution is
> found, I can submit a modified diff without it if needed.
>
> To get source/perl.c compiled I had to remove the define for
> HAVE_SYS_SYSCTL_H which triggered the #include-ing of sys/sysctl.h
> which brings in uvm/uvm_map.h. This causes a conflict, since
>> #define min_offset header.start
>> #define max_offset header.end
rather than patch, I think it's better to use this in the Makefile:
# conflict between Perl embed headers and uvm_map's {max,min}_offset defines.
CONFIGURE_ENV= ac_cv_header_sys_sysctl_h=no
[UPDATE] libgcrypt-1.4.4
Hi.
This diff updates libgcrypt to the latest stable release.
Complete ChangeLog is available under ${WRKSRC}/src/ChangeLog
It passes regress on i386.
Comments?
Index: Makefile
===
RCS file: /cvs/ports/security/libgcrypt/Makefile,v
retrieving revision 1.16
diff -u -r1.16 Makefile
--- Makefile10 Apr 2009 15:30:49 - 1.16
+++ Makefile11 Apr 2009 10:53:17 -
@@ -2,14 +2,13 @@
COMMENT= crypto library based on code used in GnuPG
-DISTNAME= libgcrypt-1.4.3
-PKGNAME= ${DISTNAME}p0
+DISTNAME= libgcrypt-1.4.4
CATEGORIES=security
-SHARED_LIBS= gcrypt 14.0
+SHARED_LIBS= gcrypt 15.0 # .16.2
HOMEPAGE= http://www.gnu.org/directory/security/libgcrypt.html
-# GPLv2
+# GPLv2/LGPLv2
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP=Yes
PERMIT_DISTFILES_CDROM=Yes
Index: distinfo
===
RCS file: /cvs/ports/security/libgcrypt/distinfo,v
retrieving revision 1.6
diff -u -r1.6 distinfo
--- distinfo26 Oct 2008 10:39:27 - 1.6
+++ distinfo11 Apr 2009 10:53:17 -
@@ -1,5 +1,5 @@
-MD5 (libgcrypt-1.4.3.tar.gz) = NmCD4NKlZayGgkXwqECInA==
-RMD160 (libgcrypt-1.4.3.tar.gz) = WLDkJvZdHFZvMyQPTTCSTABXxR0=
-SHA1 (libgcrypt-1.4.3.tar.gz) = PZ1YNQHOlRWW+n3TZnr9NXrH0FY=
-SHA256 (libgcrypt-1.4.3.tar.gz) = GZsIr8ibHB39rrGdxMLd+WPEv2iqEtZoBSAF+fIS/OI=
-SIZE (libgcrypt-1.4.3.tar.gz) = 1357080
+MD5 (libgcrypt-1.4.4.tar.gz) = nm3Pf+8a6WtXIHod6R/apA==
+RMD160 (libgcrypt-1.4.4.tar.gz) = ikz/LiXAPNeol9lwwbvowdweEFQ=
+SHA1 (libgcrypt-1.4.4.tar.gz) = bxVlk84IM4VrWVgKfUMNClFTsyQ=
+SHA256 (libgcrypt-1.4.4.tar.gz) = fAq2LKe72FS5MSTABgD8Uxnx2uu+ATiF8iw/q2hy83Q=
+SIZE (libgcrypt-1.4.4.tar.gz) = 1419876
Index: patches/patch-src_hmac256_c
===
RCS file: patches/patch-src_hmac256_c
diff -N patches/patch-src_hmac256_c
--- patches/patch-src_hmac256_c 26 Oct 2008 10:39:27 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,13 +0,0 @@
-Fix alignment issue on sparc64.
-$OpenBSD: patch-src_hmac256_c,v 1.1 2008/10/26 10:39:27 landry Exp $
src/hmac256.c.orig Thu Oct 16 13:51:12 2008
-+++ src/hmac256.c Thu Oct 16 13:51:40 2008
-@@ -271,7 +271,7 @@ finalize (hmac256_context_t hd)
- /* Store the digest into hd->buf. */
- p = hd->buf;
- #ifdef WORDS_BIGENDIAN
--#define X(a) do { *(u32*)p = hd->h##a ; p += 4; } while(0)
-+#define X(a) do { memcpy(p, &hd->h##a, sizeof(u32)); p += 4; } while(0)
- #else /* little endian */
- #define X(a) do { *p++ = hd->h##a >> 24; *p++ = hd->h##a >> 16;\
- *p++ = hd->h##a >> 8; *p++ = hd->h##a; } while(0)
--
Antoine
Re: EPIC4 perl flavor
Stuart Henderson wrote:
On 2009/04/10 21:11, James Wright wrote:
Attached patch for EPIC4 adding a perl flavor which lets you run perl
scripts. Also included is 'CFLAGS+= -O0' which fixes a problem (on
i386 at least), where hitting ctl-C (to add colours), hangs EPIC. If
the latter needs to stay in my private tree until a better solution is
found, I can submit a modified diff without it if needed.
To get source/perl.c compiled I had to remove the define for
HAVE_SYS_SYSCTL_H which triggered the #include-ing of sys/sysctl.h
which brings in uvm/uvm_map.h. This causes a conflict, since
#define min_offset header.start
#define max_offset header.end
rather than patch, I think it's better to use this in the Makefile:
# conflict between Perl embed headers and uvm_map's {max,min}_offset defines.
CONFIGURE_ENV= ac_cv_header_sys_sysctl_h=no
Updated patch to do that. The autotools are not some of my favourite
things, so I don't always see the auto* solution if a patch of a .in or
.am file works. But I always prefer the more correct fix, like this,
even if has to be shown to me, heh.
Index: Makefile
===
RCS file: /cvs/ports/net/epic4/Makefile,v
retrieving revision 1.65
diff -u -r1.65 Makefile
--- Makefile31 Mar 2009 13:31:18 - 1.65
+++ Makefile11 Apr 2009 11:46:06 -
@@ -5,7 +5,7 @@
VERSION= 2.10
HELP_DATE= 20050315
DISTNAME= epic4-${VERSION}
-PKGNAME= ${DISTNAME}p0
+PKGNAME= ${DISTNAME}p1
CATEGORIES=net
MASTER_SITES= ftp://ftp.epicsol.org/pub/epic/EPIC4-PRODUCTION/
DISTFILES= epic4-${VERSION}.tar.bz2 epic4-help-${HELP_DATE}.tar.gz
@@ -17,6 +17,10 @@
PERMIT_PACKAGE_FTP=Yes
PERMIT_DISTFILES_CDROM=Yes
PERMIT_DISTFILES_FTP= Yes
+
+FLAVORS=perl
+FLAVOR ?=
+
WANTLIB= c crypto m ncurses ssl
DESTDIRNAME= IP
@@ -25,8 +29,20 @@
SEPARATE_BUILD=simple
CONFIGURE_STYLE= gnu
-CONFIGURE_ARGS=--without-perl \
- --without-tcl
+# conflict between Perl embed headers and uvm_map's
+# {max,min}_offset defines.
+CONFIGURE_ENV= ac_cv_header_sys_sysctl_h=no
+# use a lower optimisation level prevents random hangs
+CFLAGS+= -O0
+
+CONFIGURE_ARGS=--without-tcl
+
+.if ${FLAVOR:L:Mperl}
+CONFIGURE_ARGS+=--enable-perl
+WANTLIB+= perl util
+.else
+CONFIGURE_ARGS+=--without-perl
+.endif
INSTALL_TARGET=install installhelp
Index: pkg/DESCR
===
RCS file: /cvs/ports/net/epic4/pkg/DESCR,v
retrieving revision 1.4
diff -u -r1.4 DESCR
--- pkg/DESCR 15 Dec 2003 21:55:02 - 1.4
+++ pkg/DESCR 11 Apr 2009 11:46:06 -
@@ -3,3 +3,6 @@
compatibility is undesirable have been found and fixed. No gratuitous
incompatibilities have been added, but lots of new code has been added to
make EPIC the best ircII client available.
+
+Flavor:
+ perl: script and control EPIC4 with Perl
Index: pkg/PLIST
===
RCS file: /cvs/ports/net/epic4/pkg/PLIST,v
retrieving revision 1.36
diff -u -r1.36 PLIST
--- pkg/PLIST 14 Jun 2008 02:01:10 - 1.36
+++ pkg/PLIST 11 Apr 2009 11:46:06 -
@@ -1,5 +1,5 @@
@comment $OpenBSD: PLIST,v 1.36 2008/06/14 02:01:10 pvalchev Exp $
-...@bin bin/epic
+bin/epic
@bin bin/epic-EPIC4-${VERSION}
@bin libexec/wserv4
@man man/man1/epic.1
Re: [new] www/varnish version 2.0.4
On Fri, Apr 10, 2009 at 06:13:00PM +0100, Federico G. Schwindt wrote: > On Thu, Apr 02, 2009 at 11:24:17PM +0100, Stuart Henderson wrote: > > On 2009/04/02 22:26, Toni Mueller wrote: > > > Please test and report any breakage. > > > > a couple of things are needed ports-wise, I don't have time to learn > > how to configure this at the moment to test how the software works on > > OpenBSD though. > > is anyone looking into commiting this? Ok, here's an updated version, taking into account what Stuart mentioned, plus a few other things: - Create /var/varnish by default - Use _varnish. Nothing should use nobody, not even by default - Use kqueue - Use -pthread - Do not hardcode -O2 - Install getting-started.html And some other minor tweaks. Comments? f.- varnish-2.0.4.tar.gz Description: application/tar-gz
[NEW] net/sipcalc
Sipcalc is much like net/ipcalc, but it with v6 support. Also BSD-licensed. Latest release is from 2006. Port attached. ok? Stefan sipcalc.tar.gz Description: application/tar-gz
Re: Extending libfprint
On Fri, Apr 10, 2009 at 11:39:10PM -0700, J.C. Roberts wrote: > On Sat, 4 Apr 2009 18:04:48 -0400 Jason Dixon > wrote: > > > On Sat, Apr 04, 2009 at 05:54:22PM -0400, Aaron W. Hsu wrote: > > > Hey Toby, > > > > > > From weing...@tepid.org Fri Apr 3 16:07:44 2009 > > > Subject: Re: Extending libfprint > > > > > > If any of you guys can track down the programming > > > documentation, that would be a good start to having this type of > > > device supported... > > > > > > Just a thought, but it seems that my Lenovo T500 has an AES2810 > > > from AuthenTec. Checking their website, it appears that one of the > > > things they do is provide SDKs to interested parties. I have not > > > figured out what counts as a qualifying request to get the SDK, but > > > I just thought I would ask whether anyone else has tried to obtain > > > the documentation directly from them in this form and whether it > > > works if they did get it? Is Authentec just another one of those > > > companies which refuse to give out the documentation without a host > > > of NDAs and the like? > > > > From what I've read on the libfprint mailing list, yes. > > Is it worth the time to put AuthenTec on my open specs hit-list? You have a good track record on these. I'll selfishly say yes. ;) > Off the top of my head, there's only one system here with a finger > scanner, Fujitsu Lifeboox 820... and I haven't even touched the damn > thing. In short, I don't keep up with laptop development that much, so > I'm not sure how prevalent these devices are? Thinkpads have had the option for a while now. I'm not sure about other vendors. P.S. I look at these devices as "convenience" options, not as security features. The ability to bypass them is well documented. But it would be neat to login to my laptop at home with just a quick scan. -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net/
Re: gcc 4.2 update
On Fri, 10 Apr 2009 01:18:17 +0200 Marc Espie wrote: > I finally got time to update the gcc port to something more recent. > It no longer makes sense to use a snapshot in my opinion. > > I've rebuilt the adastrap stuff (not 100% I'm current built with > libc.so.50*) > > Since there are actual users of this gcc version, please tell me if > you see any issues. > > I'd like to know if any of the relevant arches no longer work. > > I'm aware there is related work going on, such as gcj-enabling work. > I expect these ports changes to be mostly unrelated... > I've attached the full portslogger of `make regress` since just the stats are not exactly helpful. # make regress 2>&1 | /usr/ports/infrstructure/portslogger . The `make regress` fails while testing acats support. Running -current from Mar 28, on i386. -- J.C. Roberts gcc-4.2.4.log Description: Binary data
Re: [new] www/varnish version 2.0.4
* Federico G. Schwindt [090411 08:28]: > On Fri, Apr 10, 2009 at 06:13:00PM +0100, Federico G. Schwindt wrote: > > On Thu, Apr 02, 2009 at 11:24:17PM +0100, Stuart Henderson wrote: > > > On 2009/04/02 22:26, Toni Mueller wrote: > > > > Please test and report any breakage. > > > > > > a couple of things are needed ports-wise, I don't have time to learn > > > how to configure this at the moment to test how the software works on > > > OpenBSD though. > > > > is anyone looking into commiting this? > > Ok, here's an updated version, taking into account what Stuart mentioned, > plus a few other things: > > - Create /var/varnish by default > - Use _varnish. Nothing should use nobody, not even by default > - Use kqueue > - Use -pthread > - Do not hardcode -O2 > - Install getting-started.html > > And some other minor tweaks. > Comments? > > f.- Have you tested this with kqueue? Last time I tried, the code needed some fixing to work correctly. Poll on other hand worked just fine. Note, I didn't look at your patches, just raising a flag based on what I knew from previous experience... Jim
port for a python module question
hi there, i am only a sunday porter and always run into difficulties. to save the hassle of compiling all the dependencies of a given port, in the past, it was always possible for me to "cheat" the system by installing binary ports of said dependencies, and just extract their port files (i dont have all of ports.tar.gz extracted). i dont know if this is cheating really, but makes sense for me. this time i am trying to update my py-gdata port. i downloaded the new distfile, created new checksums, but i cant get past extraction this time: $ make extract ===> Checking files for py-gdata-1.3.0 `/usr/ports/distfiles/gdata-1.3.0.tar.gz' is up to date. >> (SHA256) gdata-1.3.0.tar.gz: OK ===> py-gdata-1.3.0 depends on: python-2.5* - not found ===> Verifying install for python-2.5* in lang/python/2.5 ===> Returning to build of py-gdata-1.3.0 ===> py-gdata-1.3.0 depends on: python-2.5* - not found ===> Verifying install for python-2.5* in lang/python/2.5 ===> Returning to build of py-gdata-1.3.0 Dependency check failed *** Error code 1 Stop in /home/f/src/mystuff/devel/py-gdata (line 1604 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /home/f/src/mystuff/devel/py-gdata (line 2001 of /usr/ports/infrastructure/mk/bsd.port.mk). none of this really makes sense to me. why is the check executed twice, and more importantly why does it fail? i have updated /usr/ports/infrastructure and /usr/share/mk from cvs, the result is the same. /usr/ports/mystuff is a symbolic link into my home. -f -- new restaurant on the moon. great food, no atmosphere.
Re: port for a python module question
On 2009/04/11 21:31, frantisek holop wrote: > hi there, > > i am only a sunday porter and always run into difficulties. > > to save the hassle of compiling all the dependencies of a given > port, in the past, it was always possible for me to "cheat" the > system by installing binary ports of said dependencies, and just > extract their port files (i dont have all of ports.tar.gz extracted). > i dont know if this is cheating really, but makes sense for me. > > this time i am trying to update my py-gdata port. i downloaded > the new distfile, created new checksums, but i cant get past > extraction this time: > > $ make extract > ===> Checking files for py-gdata-1.3.0 > `/usr/ports/distfiles/gdata-1.3.0.tar.gz' is up to date. > >> (SHA256) gdata-1.3.0.tar.gz: OK > ===> py-gdata-1.3.0 depends on: python-2.5* - not found > ===> Verifying install for python-2.5* in lang/python/2.5 > ===> Returning to build of py-gdata-1.3.0 > ===> py-gdata-1.3.0 depends on: python-2.5* - not found > ===> Verifying install for python-2.5* in lang/python/2.5 > ===> Returning to build of py-gdata-1.3.0 > Dependency check failed > *** Error code 1 > > Stop in /home/f/src/mystuff/devel/py-gdata (line 1604 of > /usr/ports/infrastructure/mk/bsd.port.mk). > *** Error code 1 > > Stop in /home/f/src/mystuff/devel/py-gdata (line 2001 of > /usr/ports/infrastructure/mk/bsd.port.mk). > > > none of this really makes sense to me. why is the check > executed twice, and more importantly why does it fail? > > i have updated /usr/ports/infrastructure and /usr/share/mk > from cvs, the result is the same. /usr/ports/mystuff > is a symbolic link into my home. > > -f > -- > new restaurant on the moon. great food, no atmosphere. > you need to update python.port.mk.
Re: [new] www/varnish version 2.0.4
On Sat, Apr 11, 2009 at 01:58:32PM -0400, Jim Razmus wrote: > * Federico G. Schwindt [090411 08:28]: > > On Fri, Apr 10, 2009 at 06:13:00PM +0100, Federico G. Schwindt wrote: > > > On Thu, Apr 02, 2009 at 11:24:17PM +0100, Stuart Henderson wrote: > > > > On 2009/04/02 22:26, Toni Mueller wrote: > > > > > Please test and report any breakage. > > > > > > > > a couple of things are needed ports-wise, I don't have time to learn > > > > how to configure this at the moment to test how the software works on > > > > OpenBSD though. > > > > > > is anyone looking into commiting this? > > > > Ok, here's an updated version, taking into account what Stuart mentioned, > > plus a few other things: > > > > - Create /var/varnish by default > > - Use _varnish. Nothing should use nobody, not even by default > > - Use kqueue > > - Use -pthread > > - Do not hardcode -O2 > > - Install getting-started.html > > > > And some other minor tweaks. > > Comments? > > > > f.- > > Have you tested this with kqueue? Last time I tried, the code needed > some fixing to work correctly. Poll on other hand worked just fine. Like the ones commited in 2.0.4? > Note, I didn't look at your patches, just raising a flag based on what I > knew from previous experience... Yes, I did test it, but more test won't hurt. f.-
Re: port for a python module question
hmm, on Sat, Apr 11, 2009 at 09:23:24PM +0100, Stuart Henderson said that > you need to update python.port.mk. my bad, i just downloaded a snapshot ports.tar.gz -f -- no sense being pessimistic. it wouldn't work anyway.
Re: port for a python module question
On Sun, Apr 12, 2009 at 12:18:17AM +0200, frantisek holop wrote: > hmm, on Sat, Apr 11, 2009 at 09:23:24PM +0100, Stuart Henderson said that > > you need to update python.port.mk. > > my bad, i just downloaded a snapshot ports.tar.gz If you need/must to be bandwidth efective you can use cvs(1) to update your ports.tar.gz to the latest version. You probably know that, but that doesn't hurt to remind ppl that. It's simple and prone to errors. -- best regards q#
[update] py-gdata to 1.3.0
hi there,
please test this update for py-gdata.
-f
--
drinking kills brain cells, but just the weak ones...
Index: Makefile
===
RCS file: /cvs/ports/devel/py-gdata/Makefile,v
retrieving revision 1.5
diff -u -r1.5 Makefile
--- Makefile15 Mar 2009 12:49:35 - 1.5
+++ Makefile11 Apr 2009 22:55:32 -
@@ -2,9 +2,9 @@
COMMENT= Python client library for Google data APIs
-MODPY_EGG_VERSION=1.2.4
-DISTNAME= gdata.py-${MODPY_EGG_VERSION}
-PKGNAME= py-gdata-${MODPY_EGG_VERSION}p0
+MODPY_EGG_VERSION=1.3.0
+DISTNAME= gdata-${MODPY_EGG_VERSION}
+PKGNAME= py-gdata-${MODPY_EGG_VERSION}
CATEGORIES=devel
HOMEPAGE= http://code.google.com/p/gdata-python-client/
Index: distinfo
===
RCS file: /cvs/ports/devel/py-gdata/distinfo,v
retrieving revision 1.4
diff -u -r1.4 distinfo
--- distinfo2 Feb 2009 11:58:11 - 1.4
+++ distinfo11 Apr 2009 22:55:32 -
@@ -1,5 +1,5 @@
-MD5 (gdata.py-1.2.4.tar.gz) = Uh8zo3fWT4plBboRlBW3hw==
-RMD160 (gdata.py-1.2.4.tar.gz) = QII5enGAGYwZY/3nJruRw2DyfiA=
-SHA1 (gdata.py-1.2.4.tar.gz) = W2gEz7O87QLH6fEC+ipxQUD2L9g=
-SHA256 (gdata.py-1.2.4.tar.gz) = /F3bj3axer1yhyGg4Bd+o19VpwEG9E3JAQsi7OsGq94=
-SIZE (gdata.py-1.2.4.tar.gz) = 797525
+MD5 (gdata-1.3.0.tar.gz) = d/hEA/HTusb0j2NORstNdg==
+RMD160 (gdata-1.3.0.tar.gz) = jdUMHnuv0cy0Szs+ozFK8j5f/Yo=
+SHA1 (gdata-1.3.0.tar.gz) = W31wydtF+3kDG4vyWf3cuU6QIdg=
+SHA256 (gdata-1.3.0.tar.gz) = itWgJwNFU62UpmVA4Y5nBKHd6J6Cm8WHeWyXGFq8EhM=
+SIZE (gdata-1.3.0.tar.gz) = 855353
Index: pkg/PLIST
===
RCS file: /cvs/ports/devel/py-gdata/pkg/PLIST,v
retrieving revision 1.4
diff -u -r1.4 PLIST
--- pkg/PLIST 2 Feb 2009 11:58:11 - 1.4
+++ pkg/PLIST 11 Apr 2009 22:55:32 -
@@ -27,7 +27,7 @@
lib/python${MODPY_VERSION}/site-packages/atom/url.py
lib/python${MODPY_VERSION}/site-packages/atom/url.pyc
lib/python${MODPY_VERSION}/site-packages/gdata/
-lib/python${MODPY_VERSION}/site-packages/gdata.py-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info
+lib/python${MODPY_VERSION}/site-packages/gdata-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info
lib/python${MODPY_VERSION}/site-packages/gdata/Crypto/
lib/python${MODPY_VERSION}/site-packages/gdata/Crypto/Cipher/
lib/python${MODPY_VERSION}/site-packages/gdata/Crypto/Cipher/__init__.py
@@ -91,6 +91,11 @@
lib/python${MODPY_VERSION}/site-packages/gdata/apps/emailsettings/__init__.pyc
lib/python${MODPY_VERSION}/site-packages/gdata/apps/emailsettings/service.py
lib/python${MODPY_VERSION}/site-packages/gdata/apps/emailsettings/service.pyc
+lib/python${MODPY_VERSION}/site-packages/gdata/apps/groups/
+lib/python${MODPY_VERSION}/site-packages/gdata/apps/groups/__init__.py
+lib/python${MODPY_VERSION}/site-packages/gdata/apps/groups/__init__.pyc
+lib/python${MODPY_VERSION}/site-packages/gdata/apps/groups/service.py
+lib/python${MODPY_VERSION}/site-packages/gdata/apps/groups/service.pyc
lib/python${MODPY_VERSION}/site-packages/gdata/apps/migration/
lib/python${MODPY_VERSION}/site-packages/gdata/apps/migration/__init__.py
lib/python${MODPY_VERSION}/site-packages/gdata/apps/migration/__init__.pyc
@@ -135,9 +140,16 @@
lib/python${MODPY_VERSION}/site-packages/gdata/exif/
lib/python${MODPY_VERSION}/site-packages/gdata/exif/__init__.py
lib/python${MODPY_VERSION}/site-packages/gdata/exif/__init__.pyc
+lib/python${MODPY_VERSION}/site-packages/gdata/gauth.py
+lib/python${MODPY_VERSION}/site-packages/gdata/gauth.pyc
lib/python${MODPY_VERSION}/site-packages/gdata/geo/
lib/python${MODPY_VERSION}/site-packages/gdata/geo/__init__.py
lib/python${MODPY_VERSION}/site-packages/gdata/geo/__init__.pyc
+lib/python${MODPY_VERSION}/site-packages/gdata/health/
+lib/python${MODPY_VERSION}/site-packages/gdata/health/__init__.py
+lib/python${MODPY_VERSION}/site-packages/gdata/health/__init__.pyc
+lib/python${MODPY_VERSION}/site-packages/gdata/health/service.py
+lib/python${MODPY_VERSION}/site-packages/gdata/health/service.pyc
lib/python${MODPY_VERSION}/site-packages/gdata/media/
lib/python${MODPY_VERSION}/site-packages/gdata/media/__init__.py
lib/python${MODPY_VERSION}/site-packages/gdata/media/__init__.pyc
@@ -160,6 +172,10 @@
lib/python${MODPY_VERSION}/site-packages/gdata/spreadsheet/service.pyc
lib/python${MODPY_VERSION}/site-packages/gdata/spreadsheet/text_db.py
lib/python${MODPY_VERSION}/site-packages/gdata/spreadsheet/text_db.pyc
+lib/python${MODPY_VERSION}/site-packages/gdata/test_config.py
+lib/python${MODPY_VERSION}/site-packages/gdata/test_config.pyc
+lib/python${MODPY_VERSION}/site-packages/gdata/test_config_template.py
+lib/python${MODPY_VERSION}/site-packages/gdata/test_config_template.pyc
lib/python${MODPY_VERSION}/site-packages/gdata/test_data.py
lib/python${MODPY_VERSION}/site-packages/gdata/test_data.pyc
lib/python${MODPY_VERSION}/site-packages/g
Re: [UPDATE] tinyproxy 1.6.4
hi there,
here is another attempt at the tinyproxy update.
the biggest change is probably the license: gpl v3
-f
--
you're old when you forget how to start your rocking chair.
Index: Makefile
===
RCS file: /cvs/ports/www/tinyproxy/Makefile,v
retrieving revision 1.17
diff -u -r1.17 Makefile
--- Makefile2 Feb 2009 12:29:16 - 1.17
+++ Makefile11 Apr 2009 23:04:12 -
@@ -2,41 +2,36 @@
COMMENT= lightweight HTTP/SSL proxy
-VERSION= 1.6.3
+VERSION= 1.6.4
DISTNAME= tinyproxy-${VERSION}
-PKGNAME= ${DISTNAME}p2
CATEGORIES=www net
-HOMEPAGE= http://tinyproxy.sourceforge.net/
+HOMEPAGE= https://www.banu.com/tinyproxy/
+MASTER_SITES= https://www.banu.com/pub/tinyproxy/1.6/
+MAINTAINER=frantisek holop
-MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=tinyproxy/}
-
-# GPL
+# GPLv3
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP=Yes
PERMIT_DISTFILES_CDROM=Yes
PERMIT_DISTFILES_FTP= Yes
+
WANTLIB= c
-USE_LIBTOOL= Yes
-CONFIGURE_STYLE= simple
+SEPARATE_BUILD=concurrent
+CONFIGURE_STYLE= gnu
CONFIGURE_ARGS+= --with-config=${SYSCONFDIR}/tinyproxy/tinyproxy.conf
-MAKE_FLAGS=CFLAGS="${CFLAGS}"
-
-CFLAGS+= "-DNDEBUG"
-
-DOCS= HT* RFC_INFO filter-howto.txt *.html
REGRESS_TARGET=check
do-install:
- ${INSTALL_PROGRAM} ${WRKSRC}/src/tinyproxy ${PREFIX}/sbin
+ ${INSTALL_PROGRAM} ${WRKBUILD}/src/tinyproxy ${PREFIX}/sbin
${INSTALL_DATA} ${WRKSRC}/doc/tinyproxy.8 ${PREFIX}/man/man8
${INSTALL_DATA_DIR} ${PREFIX}/share/doc/tinyproxy
${INSTALL_DATA_DIR} ${PREFIX}/share/examples/tinyproxy
- cd ${WRKSRC}/doc && ${INSTALL_DATA} ${DOCS} \
- ${PREFIX}/share/doc/tinyproxy
- cd ${WRKSRC}/doc && ${INSTALL_DATA} tinyproxy.conf \
- ${PREFIX}/share/examples/tinyproxy
+ ${INSTALL_DATA} ${WRKSRC}/doc/{debug,default,stats}.html \
+ ${PREFIX}/share/doc/tinyproxy
+ ${INSTALL_DATA} ${WRKSRC}/doc/tinyproxy.conf \
+ ${PREFIX}/share/examples/tinyproxy
.include
Index: distinfo
===
RCS file: /cvs/ports/www/tinyproxy/distinfo,v
retrieving revision 1.7
diff -u -r1.7 distinfo
--- distinfo5 Apr 2007 17:26:26 - 1.7
+++ distinfo11 Apr 2009 23:04:12 -
@@ -1,5 +1,5 @@
-MD5 (tinyproxy-1.6.3.tar.gz) = vRTQKbEmIbz9fucbL0iT2g==
-RMD160 (tinyproxy-1.6.3.tar.gz) = pVA9A73+AP0jLGQ7UYvWw+A03DM=
-SHA1 (tinyproxy-1.6.3.tar.gz) = TxAfKiTZuRf+4Dpl0nvbv8ifhfc=
-SHA256 (tinyproxy-1.6.3.tar.gz) = z08gBfzWnxAIfFmDmMGhVtGCe5+xHHaatlh7ex6kotw=
-SIZE (tinyproxy-1.6.3.tar.gz) = 467348
+MD5 (tinyproxy-1.6.4.tar.gz) = MVe5FZqNAF9CSM9NTWxl4g==
+RMD160 (tinyproxy-1.6.4.tar.gz) = CpFVkch/LTB1/nzyk0uYknZooXw=
+SHA1 (tinyproxy-1.6.4.tar.gz) = Gv3WqY6LH4arK2Z8DRXBJp7ao1w=
+SHA256 (tinyproxy-1.6.4.tar.gz) = 2a0jShscCA4qyTRJ5TGGEf/XJ3EzUrbqn/d9EKcbAkI=
+SIZE (tinyproxy-1.6.4.tar.gz) = 316567
Index: patches/patch-doc_tinyproxy_conf
===
RCS file: /cvs/ports/www/tinyproxy/patches/patch-doc_tinyproxy_conf,v
retrieving revision 1.1
diff -u -r1.1 patch-doc_tinyproxy_conf
--- patches/patch-doc_tinyproxy_conf2 Feb 2009 12:29:16 - 1.1
+++ patches/patch-doc_tinyproxy_conf11 Apr 2009 23:04:12 -
@@ -1,6 +1,6 @@
$OpenBSD: patch-doc_tinyproxy_conf,v 1.1 2009/02/02 12:29:16 martynas Exp $
doc/tinyproxy.conf.origFri Aug 6 19:23:48 2004
-+++ doc/tinyproxy.conf Mon Feb 2 06:41:40 2009
+--- doc/tinyproxy.conf.origSun Aug 24 06:58:43 2008
doc/tinyproxy.conf Tue Mar 24 03:09:09 2009
@@ -6,8 +6,8 @@
# Name of the user the tinyproxy daemon should switch to after the port
# has been bound.
@@ -12,3 +12,36 @@
#
# Port to listen on.
+@@ -40,25 +40,25 @@ Timeout 600
+ # /usr/share/tinyproxy
+ # /etc/tinyproxy
+ #
+-# ErrorFile 404 "/usr/share/tinyproxy/404.html"
+-# ErrorFile 400 "/usr/share/tinyproxy/400.html"
+-# ErrorFile 503 "/usr/share/tinyproxy/503.html"
+-# ErrorFile 403 "/usr/share/tinyproxy/403.html"
+-# ErrorFile 408 "/usr/share/tinyproxy/408.html"
++# ErrorFile 404 "/usr/local/share/tinyproxy/404.html"
++# ErrorFile 400 "/usr/local/share/tinyproxy/400.html"
++# ErrorFile 503 "/usr/local/share/tinyproxy/503.html"
++# ErrorFile 403 "/usr/local/share/tinyproxy/403.html"
++# ErrorFile 408 "/usr/local/share/tinyproxy/408.html"
+
+ #
+ # DefaultErrorFile: The HTML file that gets sent if there is no
+ # HTML file defined with an ErrorFile keyword for the HTTP error
+ # that has occured.
+ #
+-DefaultErrorFile "/usr/share/tinyproxy/default.html"
++DefaultErrorFile "/usr/local/share/tinyproxy/default.html"
+
+ #
+ # StatFile: The HTML file that
Re: [new] www/varnish version 2.0.4
> [..] > > - Create /var/varnish by default > - Use _varnish. Nothing should use nobody, not even by default > - Use kqueue > - Use -pthread > - Do not hardcode -O2 > - Install getting-started.html And hopefully last tarball, including all the above and the manpage fixes. f.- varnish-2.0.4.tgz Description: application/tar-gz
Re: clamav security diff
Patch for 0.95.1 which was commited to the tree recently.
freshclam works, but that's not a real test. Please test, I'm not in a
position to do that now. TIA.
--
best regards
q#
Index: Makefile
===
RCS file: /cvs/ports/security/clamav/Makefile,v
retrieving revision 1.42
diff -u -r1.42 Makefile
--- Makefile11 Apr 2009 14:13:58 - 1.42
+++ Makefile12 Apr 2009 00:17:28 -
@@ -31,11 +31,6 @@
USE_LIBTOOL= Yes
-# XXX dlopen() of modules fails with the ports-tree libltdl.
-# the bundled libltdl won't build with ports-tree libtool;
-# use bundled versions of both for now.
-LIBTOOL= ${WRKSRC}/libtool
-
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=clamav/}
CONFIGURE_STYLE=gnu
@@ -48,6 +43,8 @@
--with-user=_clamav \
--with-group=_clamav \
--disable-cr \
+ --with-ltdl-include=${LOCALBASE}/include \
+ --with-ltdl-lib=${LOCALBASE}/lib \
--with-dbdir=/var/db/clamav
REGRESS_TARGET=check
Re: port for a python module question
On Sat, 11 Apr 2009 21:31:47 +0200 frantisek holop wrote: > hi there, > > i am only a sunday porter and always run into difficulties. > > to save the hassle of compiling all the dependencies of a given > port, in the past, it was always possible for me to "cheat" the > system by installing binary ports of said dependencies, and just > extract their port files (i dont have all of ports.tar.gz extracted). > i dont know if this is cheating really, but makes sense for me. frantisek, This issue was "solved" a long time ago, but it's often forgotten since fast systems and tons of bandwidth tend to make us a bit spoilt. The following lines are out of my ~/.kshrc for -STABLE systems, but it can be adapted to non-development -CURRENT systems. The goal is to try to avoid compiling dependencies whenever packages are available. The other goal is to avoid downloading anything that you don't really need. First of all you need to set up your PKG_CACHE environment variable so any package you install from a remote source is copied and saved here. export PKG_CACHE=/arc/OpenBSD/`uname -r`/packages/`machine`/ On my system the "/arc/" directory is just where I archive things. Keeping the naming conventions used on official OpenBSD ftp servers might seem long, but it makes your life a lot easier. You also need to have your PKG_PATH set up. PKG_PATH=./ PKG_PATH=$PKG_PATH:/usr/ports/packages/no-arch/ PKG_PATH=$PKG_PATH:/usr/ports/packages/`machine`/all/ PKG_PATH=$PKG_PATH:/arc/OpenBSD/`uname -r`/packages/no-arch/ PKG_PATH=$PKG_PATH:/arc/OpenBSD/`uname -r`/packages/`machine`/ PKG_PATH=$PKG_PATH:ftp://ftp3.usa.openbsd.org/pub/OpenBSD/`uname -r`/packages/`machine`/ export PKG_PATH I'm sorry for the long line, but you get the idea. If you have your own local ftp server on your network, you can add it above the official project ftp package repository. If you have a crappy Internet connection like mine, you'll also want to adjust your FETCH_CMD to be a bit more persistent. export FETCH_CMD="ftp -p -r 5 -k 5 " The magic is in "FETCH_PACKAGES" which simply says if you're building a port, and it has dependencies, then download and install the packages of the dependencies (when possible) rather than building the dependency from source. export FETCH_PACKAGES=yes This will allow you to keep the /usr/ports tree on your system, but you'll no longer be building every single dependency. The dependencies, when available, are automatically installed from packages. The fact that you've got your PKG_PATH neatly configured means, you'll even skip the package downloading when possible and use a local package. Additionally, you can set up your DISTDIR environment variable, so all the various source tarballs you download to build ports remain neatly stored in one place outside of the ports tree. export DISTDIR=/arc/OpenBSD/distfiles/ Note that it is "DISTDIR" and not "DESTDIR" If you roll your own release(8), and make them available on your own local ftp server, the directory structure from above should look hauntingly familiar to what you already know on the public ftp servers of the project. /arc/OpenBSD /arc/OpenBSD/4.4/packages /arc/OpenBSD/4.4/packages/i386 /arc/OpenBSD/4.4/packages/no-arch /arc/OpenBSD/4.5/packages /arc/OpenBSD/4.5/packages/i386 /arc/OpenBSD/4.5/packages/no-arch /arc/OpenBSD/distfiles You can easily do all this with a single system, or with multiple systems, but the good thing is when you do upgrades from scratch (i.e. new installs), you can easily dump-restore your /arc/ directory and be on your way again without excessive downloading or dependency compiling. -- J.C. Roberts
webalizer
Since the 'old' webalizer was replaced with the Xtended, I have nothing but trouble with it. I mentioned it in here, twice, and also contacted the author of Xtended, who was quite helpful, asked for some input, logs, and finally excused him with having 'other things to do', and would revert back. He never did. Again, many times webalizer goes through, but at times it forks 20+ children until it gets stuck (needs to be manually killed), at other times, it doesn't like the standard Apache weblog and segfaults. With respect to reliability and robustness, I can only suggest to revert to the old mrunix version, which never failed me through many years. 2 sen, Uwe
