CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 10:03:14 Modified files: x11: Makefile Log message: +mono-gtk2
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 10:04:07 Modified files: lang : Makefile Log message: time to hook mono up. it works reasonably fine
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 10:00:27 Modified files: lang/mono : Makefile lang/mono/pkg : PLIST Added files: lang/mono : mono.port.mk lang/mono/patches: patch-data_mint_pc_in patch-data_mono-cairo_pc_in patch-data_mono_pc_in Log message: - fix the pkg-config files and introduce a mono module that removes all of the hardcoded library versions from the files that we provide in each mono-* port - install example config files
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 10:02:07 Log message: import of mono-gtk2: Gtk# is a .NET language binding for the GTK+ toolkit and assorted GNOME libraries. initial port from bernd@; update and fixes from me Status: Vendor Tag: robert Release Tags: robert_20081016 N ports/x11/mono-gtk2/Makefile N ports/x11/mono-gtk2/distinfo N ports/x11/mono-gtk2/patches/patch-parser_gapi-2_0_pc_in N ports/x11/mono-gtk2/patches/patch-gtk_gtk-sharp-2_0_pc_in N ports/x11/mono-gtk2/patches/patch-glade_glade-sharp-2_0_pc_in N ports/x11/mono-gtk2/patches/patch-glib_glib-sharp-2_0_pc_in N ports/x11/mono-gtk2/patches/patch-gtkdotnet_gtk-dotnet-2_0_pc_in N ports/x11/mono-gtk2/pkg/DESCR N ports/x11/mono-gtk2/pkg/PLIST N ports/x11/mono-gtk2/pkg/PFRAG.shared No conflicts created by this import
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 10:26:44 Modified files: net/bitlbee: Makefile distinfo Log message: I just released BitlBee 1.2.2, and I advice public server maintainers to upgrade their BitlBee daemons as soon as possible, since this release fixes a security bug that was probably there for a long time already. more info, bitlbee.org tested by merdely@, wcmaier@, Andrew Dalgleish, Wiktor Izdebski ok merdely@, wcmaier@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 11:01:16 Modified files: games/tuxpaint-stamps: Makefile distinfo games/tuxpaint-stamps/pkg: PLIST Log message: - update to tuxpaint-stamps-20080630
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 11:01:36 Modified files: games/tuxpaint : Makefile distinfo games/tuxpaint/patches: patch-Makefile patch-src_im_c patch-src_manpage_tuxpaint_1 games/tuxpaint/pkg: PLIST Added files: games/tuxpaint/pkg: PFRAG.shared Log message: - update to tuxpaint-0.9.20 - fix depends - use SUBST_CMD
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 11:03:08 Modified files: games/gcompris : Makefile distinfo games/gcompris/patches: patch-Makefile_in patch-configure patch-src_Makefile_in patch-src_boards_erase_c patch-src_gcompris_Makefile_in games/gcompris/pkg: PLIST Log message: - update to gcompris-8.4.7
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 11:29:33 Modified files: audio/herrie : Makefile distinfo audio/herrie/patches: patch-herrie_conf_sample audio/herrie/pkg: PLIST Log message: - update herrie to 2.2
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 12:14:09 Modified files: net/mcabber: Makefile distinfo net/mcabber/pkg: PLIST Log message: - update mcabber to 0.9.9 by Simon Kuhnle via Markus Hennecke (MAINTAINER)
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 12:32:19 Modified files: sysutils : Makefile Log message: +eventlog
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 13:40:31 Modified files: sysutils/god : Makefile sysutils/god/patches: patch-lib_god_contacts_email_rb Log message: let the mta add a proper date header bump pkgname
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 13:52:51 Modified files: devel : Makefile Log message: s/p5-Devel-PAR/p5-PAR/
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 14:31:22 Modified files: devel : Makefile Log message: sort
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 14:48:08 Log message: import of mono-gnome-2.20.0 Gnome# is a .NET language binding for assorted GNOME libraries. Status: Vendor Tag: robert Release Tags: robert_20081016 N ports/x11/gnome/mono-gnome/Makefile N ports/x11/gnome/mono-gnome/distinfo N ports/x11/gnome/mono-gnome/patches/patch-gconf_GConf_gconf-sharp-2_0_pc_in N ports/x11/gnome/mono-gnome/patches/patch-gconf_GConf_PropertyEditors_gconf-sharp-peditors-2_0_pc_in N ports/x11/gnome/mono-gnome/patches/patch-gnome_gnome-sharp-2_0_pc_in N ports/x11/gnome/mono-gnome/patches/patch-art_art-sharp-2_0_pc_in N ports/x11/gnome/mono-gnome/patches/patch-gnomevfs_gnome-vfs-sharp-2_0_pc_in N ports/x11/gnome/mono-gnome/pkg/PLIST N ports/x11/gnome/mono-gnome/pkg/PFRAG.shared N ports/x11/gnome/mono-gnome/pkg/DESCR No conflicts created by this import
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 15:47:10 Modified files: lang/mono : Makefile mono.port.mk Log message: - set CATEGORIES+=lang/mono via mono.port.mk, instead of every port doing it themselves. like other modules do too.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 15:48:33 Modified files: x11/gnome/mono-gnome: Makefile Log message: - CATEGORIES+=lang/mono is now set via mono.port.mk
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 15:47:54 Modified files: x11/mono-gtk2 : Makefile Log message: - CATEGORIES+=lang/mono is now set via mono.port.mk
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 16:15:06 Modified files: x11/gnome/mono-gnome: Makefile Log message: - use gnome.port.mk - specify license version
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 16:36:02 Modified files: geo/openbsd-developers: Makefile geo/openbsd-developers/files: OpenBSD Log message: Add my ICBM coordinates, bump version OK jasper@, robert@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: [EMAIL PROTECTED] 2008/10/16 17:35:50 Modified files: infrastructure/package: gen-package-pages Log message: bring up to speed for 4.4
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs
Module name:ports
Changes by: [EMAIL PROTECTED] 2008/10/16 23:58:56
Modified files:
x11/gnome/mono-gnome: Makefile
Log message:
{RUN,BUILD}_DEPEND on lang/mono
Re: mystuff. mystuff?
frantisek holop schrieb: hi there, i was wondering where 'mystuff' comes from... i know it has a lot of history and some people feel very fondly about it, but i can't help that it kind of reminds me the failed naming scheme from redmond (my computer, etc)... i think /usr/ports/local/ is more openbsd-y and kind of more professional (or perhaps not). i am not asking for changing or removing 'mystuff', rather to consider the addition of 'local' as a legal 'mystuff' directory please share your comments. -f name it what you like, and add it to PORTSDIR_PATH. that's how i do it (moved the mystuff dir to different location... it's too easy to rm -rf /usr/ports).
Re: mystuff. mystuff?
On 2008/10/16 08:49, Julian Leyh wrote: frantisek holop schrieb: hi there, i was wondering where 'mystuff' comes from... i know it has a lot of history and some people feel very fondly about it, but i can't help that it kind of reminds me the failed naming scheme from redmond (my computer, etc)... i think /usr/ports/local/ is more openbsd-y and kind of more professional (or perhaps not). i am not asking for changing or removing 'mystuff', rather to consider the addition of 'local' as a legal 'mystuff' directory please share your comments. -f name it what you like, and add it to PORTSDIR_PATH. that's how i do it (moved the mystuff dir to different location... it's too easy to rm -rf /usr/ports). $ grep -r mystuff /usr/ports/infrastructure
Re: pkg_add problems (my fault?)
Hi, On Tue, 14.10.2008 at 11:58:41 +0200, Marc Espie [EMAIL PROTECTED] wrote: On Tue, Oct 14, 2008 at 09:58:11AM +0200, Toni Mueller wrote: * pkg_add does also not seem to support stacked repositories (I don't have a better name for this). I mean: If I use eg. my $PKG_CACHE first within my $PKG_PATH to find packages on my disk first, pkg_add does not seem to resolve any other package names not present in $PKG_CACHE. The same seems to be true for online repositories. Not quite the whole story. It works like -L for ld: it stops at the first repository that contains packages that match what you ask for. I was so far under the impression that pkg_add locks in on the first repository it can access, and disregards all other repositories in the path. At least, I experienced problems like this (contrived example, after having had the problem some months ago): PKG_PATH=localrepo:mirror1:mirror2 pkg_add unoffical1 official2 with 'unofficial1' being present in 'localrepo', then it would try to find 'official2' in 'localrepo', too, and barfs if it doesn't find it there. Similar story for different versions of a package in different repositories. But I'll double-check with your most recent code again. This prevents me from having local repositories that contain only unofficial stuff, and having official mirrors as a fallback option only. I don't understand that paragraph. If you have only unofficial stuff in the local repositories, then you're good. It will interfere only when it needs to. I usually have both in my local repository. On the other hand, PKG_CACHE is mostly there to allow you to reinstall a set of boxen quickly after installing the first one... While we're at it, I found that mirrors often shut the connection down in the middle due to too frequent accesses (purported DoS attacks) while running pkg_add -ui. Maybe one can take a leaf out of Debian's book about package management and download only lists of packages from any one mirror, and later get the files in a second run, but all in one go. Just my 0.02 cents... -- Kind regards, --Toni++
Re: pkg_info -E
Hi, On Wed, 15.10.2008 at 22:22:32 +0200, frantisek holop [EMAIL PROTECTED] wrote: a bit of an odd choice if you ask me, first i was looking for -l/-L for locate or something. but those are already taken for some even more obscure functions i have never used :] I didn't check for -l, but the usage of -L is the same as it is for dpkg, where -L also lists the contents of a package. It looks like this is simply a matter of customs. Kind regards, --Toni++
[UPDATE] mail/msmtp
Here's an update for msmtp, please test! (patch -E)
From: Tim van der Molen [EMAIL PROTECTED]. Thank you!
--
Everything is simple, we're stupid.
gopher://sdf.lonestar.org/1/users/bulibuta
Index: Makefile
===
RCS file: /cvs/ports/mail/msmtp/Makefile,v
retrieving revision 1.14
diff -u -r1.14 Makefile
--- Makefile19 Jun 2008 09:09:42 - 1.14
+++ Makefile15 Oct 2008 01:17:20 -
@@ -2,8 +2,7 @@
COMMENT= SMTP plugin for MUAs
-DISTNAME= msmtp-1.4.13
-PKGNAME= ${DISTNAME}p1
+DISTNAME= msmtp-1.4.16
CATEGORIES=mail
HOMEPAGE= http://msmtp.sourceforge.net/
@@ -39,7 +38,7 @@
${INSTALL_DATA} ${WRKSRC}/doc/msmtp.html ${PREFIX}/share/doc/msmtp
${INSTALL_DATA} ${WRKSRC}/scripts/msmtpqueue/{README,ChangeLog} \
${PREFIX}/share/msmtp/msmtpqueue
- ${INSTALL_SCRIPT} ${WRKSRC}/scripts/set_sendmail.sh \
+ ${INSTALL_SCRIPT} ${WRKSRC}/scripts/set_sendmail/set_sendmail.sh \
${PREFIX}/share/examples/msmtp
${INSTALL_SCRIPT} ${WRKSRC}/scripts/msmtpqueue/*.sh \
${PREFIX}/share/examples/msmtp
Index: distinfo
===
RCS file: /cvs/ports/mail/msmtp/distinfo,v
retrieving revision 1.12
diff -u -r1.12 distinfo
--- distinfo28 Aug 2007 18:45:34 - 1.12
+++ distinfo15 Oct 2008 01:17:20 -
@@ -1,5 +1,5 @@
-MD5 (msmtp-1.4.13.tar.bz2) = AhqR1xRRAK0PAMkSyBBOAw==
-RMD160 (msmtp-1.4.13.tar.bz2) = qecB/PvPONJAxHTbyIYN4lne3E4=
-SHA1 (msmtp-1.4.13.tar.bz2) = wdDe4rjgNSiaBGfWh+yAZtumHpc=
-SHA256 (msmtp-1.4.13.tar.bz2) = l2TQuV69XiL1LbKwt9t2KH04AgUHmM/iqF7ay2BDGPU=
-SIZE (msmtp-1.4.13.tar.bz2) = 704779
+MD5 (msmtp-1.4.16.tar.bz2) = d6MzYB6d4D9pVTlJjmeMwg==
+RMD160 (msmtp-1.4.16.tar.bz2) = EUIEIjXkJFf4JE4C8Hjb1T81CIY=
+SHA1 (msmtp-1.4.16.tar.bz2) = eE7igc7gXkoxJinvqk6okruYpR8=
+SHA256 (msmtp-1.4.16.tar.bz2) = JI+yuB//k2J89RFx3oCspvmsSk+6Z9UztM7Znic6eEo=
+SIZE (msmtp-1.4.16.tar.bz2) = 727517
Index: patches/patch-configure
===
RCS file: /cvs/ports/mail/msmtp/patches/patch-configure,v
retrieving revision 1.6
diff -u -r1.6 patch-configure
--- patches/patch-configure 28 Aug 2007 18:45:34 - 1.6
+++ patches/patch-configure 15 Oct 2008 01:17:20 -
@@ -1,7 +1,7 @@
$OpenBSD: patch-configure,v 1.6 2007/08/28 18:45:34 jasper Exp $
configure.orig Wed Aug 1 11:00:47 2007
-+++ configure Tue Aug 28 20:26:32 2007
-@@ -903,14 +903,14 @@ localstatedir='${prefix}/var'
+--- configure.orig Mon Jul 28 00:46:30 2008
configure Tue Oct 14 13:56:57 2008
+@@ -950,14 +950,14 @@ localstatedir='${prefix}/var'
includedir='${prefix}/include'
oldincludedir='/usr/include'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
@@ -18,18 +18,18 @@
ac_prev=
ac_dashdash=
-@@ -20470,7 +20470,7 @@ REPLACE_FTELLO!$REPLACE_FTELLO$ac_delim
- REPLACE_FTELL!$REPLACE_FTELL$ac_delim
- REPLACE_FFLUSH!$REPLACE_FFLUSH$ac_delim
+@@ -21779,7 +21779,7 @@ HAVE_DECL_GETDELIM!$HAVE_DECL_GETDELIM$ac_delim
+ HAVE_DECL_GETLINE!$HAVE_DECL_GETLINE$ac_delim
+ REPLACE_GETLINE!$REPLACE_GETLINE$ac_delim
GETOPT_H!$GETOPT_H$ac_delim
-LIBINTL!$LIBINTL$ac_delim
+LIBINTL!$LTLIBINTL$ac_delim
LTLIBINTL!$LTLIBINTL$ac_delim
GNULIB_CHOWN!$GNULIB_CHOWN$ac_delim
GNULIB_DUP2!$GNULIB_DUP2$ac_delim
-@@ -20586,7 +20586,7 @@ XGETTEXT!$XGETTEXT$ac_delim
- XGETTEXT_015!$XGETTEXT_015$ac_delim
+@@ -21930,7 +21930,7 @@ XGETTEXT_015!$XGETTEXT_015$ac_delim
MSGMERGE!$MSGMERGE$ac_delim
+ XGETTEXT_EXTRA_OPTIONS!$XGETTEXT_EXTRA_OPTIONS$ac_delim
INTL_MACOSX_LIBS!$INTL_MACOSX_LIBS$ac_delim
-LIBICONV!$LIBICONV$ac_delim
+LIBICONV!$LTLIBICONV$ac_delim
Index: patches/patch-scripts_msmtpq_msmtpQ
===
RCS file: patches/patch-scripts_msmtpq_msmtpQ
diff -N patches/patch-scripts_msmtpq_msmtpQ
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-scripts_msmtpq_msmtpQ 15 Oct 2008 01:17:20 -
@@ -0,0 +1,9 @@
+$OpenBSD$
+--- scripts/msmtpq/msmtpQ.orig Mon Jul 28 00:20:47 2008
scripts/msmtpq/msmtpQ Tue Oct 14 14:18:06 2008
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env bash
++#!/bin/sh
+
+ #--
+ #
Index: patches/patch-scripts_msmtpq_msmtpq
===
RCS file: patches/patch-scripts_msmtpq_msmtpq
diff -N patches/patch-scripts_msmtpq_msmtpq
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-scripts_msmtpq_msmtpq 15 Oct 2008 01:17:20 -
@@ -0,0 +1,9 @@
+$OpenBSD$
+--- scripts/msmtpq/msmtpq.orig Mon Jul 28 00:20:41 2008
scripts/msmtpq/msmtpq Tue Oct 14 14:18:13 2008
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env bash
++#!/bin/sh
+
+ #--
+ #
Index:
[NEW] devel/ruby-linecache
LineCache - caches (Ruby source) files as might be used in a debugger or a tool that works with sets of Ruby source files. This is needed for updating ruby-debug-base and ruby-debug ports. Please test and commit (hello bernd (-:). Works fine on i386. -- Everything is simple, we're stupid. gopher://sdf.lonestar.org/1/users/bulibuta ruby-linecache.tgz Description: application/tar-gz
Re: [UPDATE] mail/msmtp
On Thu, Oct 16, 2008 at 03:12:36PM +0300, Paul Irofti wrote: Here's an update for msmtp, please test! (patch -E) From: Tim van der Molen [EMAIL PROTECTED]. Thank you! Forgot to mention that this was tested on i386 and amd64. -- Everything is simple, we're stupid. gopher://sdf.lonestar.org/1/users/bulibuta
Re: [NEW] devel/ruby-linecache
Hey Paul, Paul Irofti [Thu, Oct 16, 2008 at 04:43:58PM +0300] wrote: LineCache - caches (Ruby source) files as might be used in a debugger or a tool that works with sets of Ruby source files. This is needed for updating ruby-debug-base and ruby-debug ports. Please test and commit (hello bernd (-:). Works fine on i386. I'll take care. :) Bernd
Re: UPDATE: xmonad 0.7 to 0.8
Hello everyone, I might have a patch working and attached (well it works here and on Andrei's computer, which the most exhaustive testing I can do right now) to update to 0.8. (There is not much change going on apart from the obvious checksums) If anyone has time to spare ... -- Richard Bonichon xmonad.patch Description: Binary data
Re: pkg_info -E
hmm, on Thu, Oct 16, 2008 at 12:21:51PM +0200, Toni Mueller said that Hi, On Wed, 15.10.2008 at 22:22:32 +0200, frantisek holop [EMAIL PROTECTED] wrote: a bit of an odd choice if you ask me, first i was looking for -l/-L for locate or something. but those are already taken for some even more obscure functions i have never used :] I didn't check for -l, but the usage of -L is the same as it is for dpkg, where -L also lists the contents of a package. ah, correct, scratch -L, my mistake. -f -- which is the non-smoking lifeboat?
Re: UPDATE: sysutils/syslog-ng
Damnit!
I've been waiting for my 4.4 CDs since July/August and you beat me to
the update by 8 days. :)
I did mine as a new port, based on the old one, as some people may want
to run the 1.6.x bitrot version.
http://people.collaborativefusion.com/~seklecki/openbsd44_port_syslog-ng209_eventlog027.tar
# syslog-ng -V
syslog-ng 2.0.9
# uname -a
OpenBSD cauldron-obsd-44stable-i386 4.4 GENERIC.MP#844 i386
Lets get this bad boy tested and updated before 4.5 is released!
~BAS
# tar cvf openbsd44_port_syslogng209_etlog027.tar eventlog/ syslog-ng2/
eventlog
eventlog/Makefile
eventlog/distinfo
eventlog/pkg
eventlog/pkg/DESCR
eventlog/pkg/PLIST
eventlog/pkg/PFRAG.shared
syslog-ng2
syslog-ng2/CVS
syslog-ng2/CVS/Repository
syslog-ng2/CVS/Entries
syslog-ng2/CVS/Tag
syslog-ng2/pkg
syslog-ng2/pkg/CVS
syslog-ng2/pkg/CVS/Repository
syslog-ng2/pkg/CVS/Entries
syslog-ng2/pkg/CVS/Tag
syslog-ng2/pkg/DESCR
syslog-ng2/pkg/PLIST
syslog-ng2/pkg/PLIST.orig
syslog-ng2/pkg/MESSAGE
syslog-ng2/Makefile
syslog-ng2/distinfo
syslog-ng2/files
syslog-ng2/files/syslog-ng.conf
syslog-ng2/patches
syslog-ng2/patches/patch-tests_loggen_loggen_c
# tar tzvf /usr/ports/packages/i386/all/syslog-ng-2.0.9.tgz
-r--r--r-- 1 root wheel 721 Oct 16 11:46 +CONTENTS
-r--r--r-- 1 root wheel 568 Oct 16 11:46 +DESC
-r--r--r-- 1 root wheel 216 Oct 16 11:46 +DISPLAY
-r--r--r-- 1 root bin 5899 Oct 16 11:46 man/man5/syslog-ng.conf.5
-r--r--r-- 1 root bin 3268 Oct 16 11:46 man/man8/syslog-ng.8
-r-xr-xr-x 1 root bin1277148 Oct 16 11:46 sbin/syslog-ng
-r--r--r-- 1 root bin 8837 Oct 16 11:46 share/examples/syslog-ng.conf
-r-xr-xr-x 1 root bin 10948 Oct 16 11:46 bin/loggen
# make install
=== Verifying specs: glib-2.0 c glib-2.0
=== found glib-2.0.1600.2 c.48.0
=== Installing syslog-ng-2.0.9 from /usr/ports/packages/i386/all/
syslog-ng-2.0.9: complete
--- syslog-ng-2.0.9 ---
Add the following to rc.local(8):
if [ -x /usr/local/sbin/syslog-ng -a -f /etc/syslog-ng.conf ]; then
/usr/local/sbin/syslog-ng
echo syslog-ng2
fi
Thanks for shopping balabit.hu and company.
On Wed, 2008-10-08 at 21:34 +0200, Steven Mestdagh wrote:
this requires the new sysutils/eventlog port sent earlier.
please test/comment/ok.
Index: Makefile
===
RCS file: /cvs/ports/sysutils/syslog-ng/Makefile,v
retrieving revision 1.8
diff -u -r1.8 Makefile
--- Makefile 6 Oct 2008 16:09:13 - 1.8
+++ Makefile 8 Oct 2008 19:29:28 -
@@ -2,50 +2,39 @@
COMMENT= syslogd replacement
+DISTNAME=syslog-ng-2.1.1
CATEGORIES= sysutils
-DISTNAME=syslog-ng-1.6.8
-LIBOL= libol-0.3.16
+MAINTAINER= Steven Mestdagh [EMAIL PROTECTED]
-MAINTAINER= Jakob Schlyter [EMAIL PROTECTED]
+HOMEPAGE = http://www.balabit.com/network-security/syslog-ng/
-MASTER_SITE_SYSLOGNG=\
- http://www.balabit.com/downloads/files/syslog-ng/sources/
+# GPL v2
+PERMIT_PACKAGE_CDROM = Yes
+PERMIT_PACKAGE_FTP = Yes
+PERMIT_DISTFILES_CDROM = Yes
+PERMIT_DISTFILES_FTP = Yes
-MASTER_SITES=${MASTER_SITE_SYSLOGNG:=1.6/src/}
-MASTER_SITES0= ${MASTER_SITE_SYSLOGNG:=libol/0.3/}
+MASTER_SITES =
http://www.balabit.com/downloads/files/syslog-ng/sources/2.1/src/
-HOMEPAGE=http://www.balabit.com/products/syslog_ng/
+WANTLIB =c iconv intl wrap
-DISTFILES= ${DISTNAME}.tar.gz \
- ${LIBOL}.tar.gz:0
+LIB_DEPENDS =glib-2.0::devel/glib2 \
+ evtlog::sysutils/eventlog
-# GPL
-PERMIT_PACKAGE_CDROM=Yes
-PERMIT_PACKAGE_FTP= Yes
-PERMIT_DISTFILES_CDROM= Yes
-PERMIT_DISTFILES_FTP=Yes
-WANTLIB= c
+CONFIGURE_STYLE =gnu
+CONFIGURE_ARGS +=--enable-tcp-wrapper
-CONFIGURE_STYLE= gnu
-CONFIGURE_ARGS+= --with-libol=${WRKDIR}/${LIBOL} \
- --enable-tcp-wrapper
+DOC =${PREFIX}/share/doc/syslog-ng/
+EXAMPLES = ${PREFIX}/share/examples/syslog-ng/
-DOC= ${PREFIX}/share/doc/syslog-ng
-EXAMPLES=${PREFIX}/share/examples/syslog-ng
-
-pre-configure:
- cp -f ${PORTSDIR}/infrastructure/db/config.guess \
- ${PORTSDIR}/infrastructure/db/config.sub ${WRKDIR}/${LIBOL}
- cd ${WRKDIR}/${LIBOL}; ./configure ; ${MAKE}
+post-extract:
+ tar -C ${WRKBUILD} -xzf ${WRKSRC}/doc/reference/syslog-ng.html.tar.gz
post-install:
${INSTALL_DATA_DIR} ${DOC}
- ${INSTALL_DATA} ${WRKSRC}/doc/sgml/*.{ps,sgml,txt} ${DOC}
- (cd ${DOC} ;\
- tar xzf ${WRKSRC}/doc/sgml/syslog-ng.html.tar.gz ;\
- ln -s book1.html syslog-ng.html/index.html )
+ ${INSTALL_DATA} ${WRKBUILD}/syslog-ng.html/index.html ${DOC}
${INSTALL_DATA_DIR} ${EXAMPLES}
- ${INSTALL_DATA} ${WRKSRC}/doc/syslog-ng.conf.sample ${EXAMPLES}
+ ${INSTALL_DATA}
New port: Worker - File manager for Unix
Hello,
this is my first port. I tryed it on my thinkpad t42p and it works great. If
something is wrong, I would be very happy about your comments.
Makefile:
# $OpenBSD: Makefile,v 1.00 2008/10/16 20:00:00 cruesch Exp $
COMMENT=Worker - File manager for OpenBSD
VERSION=2.16.5
DISTNAME= worker-${VERSION}
CATEGORIES= misc
HOMEPAGE= http://www.boomerangsworld.de/cms/worker/downloads/
MAINTAINER= Christian Ruesch [EMAIL PROTECTED]
# GPL
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP= Yes
MASTER_SITES= ${HOMEPAGE}
CONFIGURE_STYLE=gnu
WANTLIB=ICE SM X11 c m pthread stdc++
.include bsd.port.mk
--
Kind regards
Christian Ruesch
Re: New port: Worker - File manager for Unix
The missing tarball can be downloaded here: http://crsc.eu/worker/ -- Kind regards Christian Ruesch
Re: New port: Worker - File manager for Unix
* Christian Ruesch wrote:
Hello,
this is my first port. I tryed it on my thinkpad t42p and it works great.
If something is wrong, I would be very happy about your comments.
Makefile:
# $OpenBSD: Makefile,v 1.00 2008/10/16 20:00:00 cruesch Exp $
Make this just
# $OpenBSD$
The rest will be added when the ports is commited (the additional data
does not harm, it will be overwritten, but it is not neede either).
COMMENT=Worker - File manager for OpenBSD
Don't repeat the name. Don't start with an upercase letter, don't
say 'for OpenBSD', this is obvious for an OpenBSD package:
:
COMMENT=file manager
Maybe 'graphical file manager'
VERSION=2.16.5
DISTNAME= worker-${VERSION}
If you don't use the VERSION variable anywhere else than in DISTNAME,
you can also do without it. I.e.
DISTNAME= worker-2.15.5
CATEGORIES= misc
Is this the right category? Have you considered x11, sysutils?
HOMEPAGE= http://www.boomerangsworld.de/cms/worker/downloads/
This is not the homepage. http://www.boomerangsworld.de/cms/worker/ is.
HOMEPAGE= http://www.boomerangsworld.de/cms/worker/
MAINTAINER= Christian Ruesch [EMAIL PROTECTED]
# GPL
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP= Yes
MASTER_SITES= ${HOMEPAGE}
Add the 'downloads/' here:
MASTER_SITES= ${HOMEPAGE}downloads/
CONFIGURE_STYLE=gnu
WANTLIB=ICE SM X11 c m pthread stdc++
.include bsd.port.mk
put a newline after WANTLIB
Besides a Makefile, a ports consists of a few more files:
pkg/DECSR
pkg/PLIST
These two are missing, but easy for you to add. You might want to
read the following man pages:
bsd.port.mk(5)
pkg_create(1)
And consult the mailing list archives and the FAQ.
--
Kind regards
Christian Ruesch
- Marc Balmer
Re: mystuff. mystuff?
frantisek holop wrote: hi there, i was wondering where 'mystuff' comes from... i know it has a lot of history and some people feel very fondly about it, but i can't help that it kind of reminds me the failed naming scheme from redmond (my computer, etc)... i think /usr/ports/local/ is more openbsd-y and kind of more professional (or perhaps not). i am not asking for changing or removing 'mystuff', rather to consider the addition of 'local' as a legal 'mystuff' directory please share your comments. -f I completely agree. When I first started writing ports, I created /usr/ports/local because it seemed logical (i.e. /usr/local). Then later I found out I needed to use /usr/ports/mystuff. No big deal, however, mystuff just seems less conventional than local in the UNIX world.
Re: New port: Worker - File manager for Unix
Thank you for your comments. Replaced the old tarball with the new one on the same download location. -- Kind regards Christian Ruesch
Re: New port: Worker - File manager for Unix
Hi Christian-
On Thu, Oct 16, 2008 at 10:20:23PM +0200, Christian Ruesch wrote:
The missing tarball can be downloaded here:
http://crsc.eu/worker/
In addition to Marc's comments, I have a few:
* pkg/DESCR should be wrapped at ~78 characters
* I get an odd hiccup during configure (log attached);
configure.ac's version check for gcc might be broken.
* It'd be nice to add devel/libmagic support (configure says
Libmagic disabled)
* License appears to be GPLv2+
Otherwise, builds fine on i386 and seems to work.
Thanks!
--
o--{ Will Maier }--o
| web:...http://www.lfod.us/ | [EMAIL PROTECTED] |
*-[ BSD: Live Free or Die ]*
Re: mystuff. mystuff?
On 2008/10/16 13:38, Clint Pachl wrote: frantisek holop wrote: hi there, i was wondering where 'mystuff' comes from... i know it has a lot of history and some people feel very fondly about it, but i can't help that it kind of reminds me the failed naming scheme from redmond (my computer, etc)... i think /usr/ports/local/ is more openbsd-y and kind of more professional (or perhaps not). i am not asking for changing or removing 'mystuff', rather to consider the addition of 'local' as a legal 'mystuff' directory please share your comments. -f I completely agree. When I first started writing ports, I created /usr/ports/local because it seemed logical (i.e. /usr/local). Then later I found out I needed to use /usr/ports/mystuff. No big deal, however, mystuff just seems less conventional than local in the UNIX world. this is ports developer stuff, you already have a lot of things to learn as it is, and whatever this is called you still have to learn it. adding more names just confuses things, and it's already mentioned in various ports tutorials...
Re: New port: Worker - File manager for Unix
* Christian Ruesch wrote: The missing tarball can be downloaded here: http://crsc.eu/worker/ ok, we are quite there... pkg/DESCR should be formatted, run it through fmt. There is a religious argument about what the right line size should be. Personally I use the fmt default, but some people object. I forgot what the political correct value was ;) Oh, I think it shoule be GPLv2 in the license marke (my fault). -- Kind regards Christian Ruesch
Re: New port: Worker - File manager for Unix
On 2008/10/16 22:53, Marc Balmer wrote: * Christian Ruesch wrote: The missing tarball can be downloaded here: http://crsc.eu/worker/ ok, we are quite there... pkg/DESCR should be formatted, run it through fmt. There is a religious argument about what the right line size should be. Personally I use the fmt default, but some people object. I use fmt default unless it looks ugly, or breaks between two related words make it hard to read, then I fiddle with line lengths by shifting words around. I forgot what the political correct value was ;) 22, ready for when OpenBSD is ported to the VIC 20.
Re: New port: Worker - File manager for Unix
On Thu, Oct 16, 2008 at 10:14:04PM +0100, Stuart Henderson wrote: pkg/DESCR should be formatted, run it through fmt. There is a religious argument about what the right line size should be. Personally I use the fmt default, but some people object. I use fmt default unless it looks ugly, or breaks between two related words make it hard to read, then I fiddle with line lengths by shifting words around. pipe it through nroff ;-)
Re: New port: Worker - File manager for Unix
I updated the license and formated the pkg/DESCR via `fmt'. About the odd hiccups during configure and the devel/libmagic support -- I have no idea what to do. :-) Thanks again for your comments. -- Kind regards Christian Ruesch
Re: mystuff. mystuff?
hmm, on Thu, Oct 16, 2008 at 09:46:15PM +0100, Stuart Henderson said that this is ports developer stuff, you already have a lot of things to learn as it is, and whatever this is called you still have to learn it. adding more names just confuses things, and it's already mentioned in various ports tutorials... i fully respect everyone's opinion, and if one doesnt like 'local' or find it as logical as me, no problem. i am aware i can tweak it myself, but that's another error vector, isn't, making my stuff (pun intended) unsupported in the ports framework. but please stop this never change stuff because it confuses things because then we could just freeze the tree forever and not correct design decision which after some time proved to be wrong (not this case mind you, generally). plenty of stuff changes all the time that are way more confusing (e.g. pf implied defaults, etc etc) -f -- every silver lining has a cloud.
potentially unsafe operations
hi there, i am just doing a full upgrade, and these messages are somewhat annoying esp because they interrupt the upgrade session and i think they could be supressed in well defined cases. what i mean is, what is potentially dangerious about @exec /usr/local/bin/gtk-update-icon-cache and @exec /usr/local/bin/update-desktop-database that most of the gtk2 progies do nowadays? what about a function for pkg_add to suppress @exec warnings for a list of external programs commonly called by ports? what do you think? i can try and make a patch, but it will take some time, i am boarding a ship from japan to vladivostok in a couple of hours :] -f -- madam i'm adam.
Re: potentially unsafe operations
On Fri, Oct 17, 2008 at 01:58:23AM +0200, frantisek holop wrote: hi there, i am just doing a full upgrade, and these messages are somewhat annoying esp because they interrupt the upgrade session and i think they could be supressed in well defined cases. see the -F switch in the manual, you probably want: $ sudo pkg_add -u -F update,alwaysupdate,updatedepends -- Everything is simple, we're stupid. gopher://sdf.lonestar.org/1/users/bulibuta
Re: potentially unsafe operations
hmm, on Fri, Oct 17, 2008 at 03:05:59AM +0300, Paul Irofti said that On Fri, Oct 17, 2008 at 01:58:23AM +0200, frantisek holop wrote: hi there, i am just doing a full upgrade, and these messages are somewhat annoying esp because they interrupt the upgrade session and i think they could be supressed in well defined cases. see the -F switch in the manual, you probably want: $ sudo pkg_add -u -F update,alwaysupdate,updatedepends update unsafe update: old packing-list will run scripts that may fail. i must admit the documentation lost me here. the way i read it, this applies to the @unexec's in the 'old' packages when uninstalling before installing the new package? and they may fail? (the scripts i am talking about do not fail.) in any case, such a list would allow a nice granularity for potentially unsafe operations vs business as usual operations.. -f -- many would be cowards if they had enough courage.
Re: mystuff. mystuff?
On Fri, Oct 17, 2008 at 01:50:01AM +0200, frantisek holop wrote: hmm, on Thu, Oct 16, 2008 at 09:46:15PM +0100, Stuart Henderson said that this is ports developer stuff, you already have a lot of things to learn as it is, and whatever this is called you still have to learn it. adding more names just confuses things, and it's already mentioned in various ports tutorials... i fully respect everyone's opinion, and if one doesnt like 'local' or find it as logical as me, no problem. i am aware i can tweak it myself, but that's another error vector, isn't, making my stuff (pun intended) unsupported in the ports framework. but please stop this never change stuff because it confuses things because then we could just freeze the tree forever and not correct design decision which after some time proved to be wrong (not this case mind you, generally). plenty of stuff changes all the time that are way more confusing (e.g. pf implied defaults, etc etc) please stop making generalizations when the discussion is about specifics. this discussion is about the name of one optional directory in the ports tree. not about all of cvs. -- [EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org
update: editors/vim 7.1.315 - 7.2.25
two happy vim users already, but i'd like to see some more test coverage -- GDB has a 'break' feature; why doesn't it have 'fix' too? vimupdate.diff.gz Description: GNU Zip compressed data
