Re: UPDATE: vpnc 0.4.0
Works OK also on zaurus 4.1-current. Rolf
Re: Proftpd port
STeve Andre' ([EMAIL PROTECTED]) shaped the electrons to say: > Security issues. Take a look at > > http://marc.info/?l=openbsd-ports&m=107325746223524&w=2 In all fairness to Proftpd, the proftpd nowadays isn't really the same animal as the proftpd of old. I remember, and I think I even contributed to, the discussion of yanking Proftpd from the ports tree back in the old days when MacGuyver (what a name!) was maintaining Proftpd. I know the current maintainer, TJ Saunders, and mentioned the whole thing to him over beers one night and he was and is fully commited to the security of Proftpd. He was pretty bummed to hear that Proftpd has such a bad rap with the OpenBSD community. Especially since he takes the security of Proftpd very seriously. I'm not saying that we should definitely include it, only that just because it was bad at some point in the past, doesn't mean it has remained that way for 6 years. AFAIK, it has been rewritten. Just my $.02, -Dave
Re: Proftpd port
On Monday 30 April 2007 20:31:47 Rafael wrote: > Why was pulled? Security, Bugs? No maintainer? > > 2007/4/30, Josh Grosse <[EMAIL PROTECTED]>: > > On Mon, Apr 30, 2007 at 09:05:14PM -0300, Rafael wrote: > > > I am using proftpd and would like to make the package of it, because I > > > did not find in the ports tree. I can construct it and send to list > > > for testing? > > > > Proftpd entered the ports tree in 1998, and was pulled (finally) in 2002: > > > > http://www.openbsd.org/cgi-bin/cvsweb/ports/net/proftpd/Attic/Makefile Security issues. Take a look at http://marc.info/?l=openbsd-ports&m=107325746223524&w=2 In general, looking at the mailing list archives is a really good thing to do before asking about something. One way you can get to the archives is by going to the openbsd web site, and looking for mailing lists on the front page, and then following down to the list of archives. I use the MARC archive, and looked in the ports list for the above pointer. The archives almost always answer my questions on things. --STeve Andre'
Re: Proftpd port
Why was pulled? Security, Bugs? No maintainer? 2007/4/30, Josh Grosse <[EMAIL PROTECTED]>: On Mon, Apr 30, 2007 at 09:05:14PM -0300, Rafael wrote: > I am using proftpd and would like to make the package of it, because I > did not find in the ports tree. I can construct it and send to list > for testing? Proftpd entered the ports tree in 1998, and was pulled (finally) in 2002: http://www.openbsd.org/cgi-bin/cvsweb/ports/net/proftpd/Attic/Makefile
Re: Proftpd port
On Mon, Apr 30, 2007 at 09:05:14PM -0300, Rafael wrote: > I am using proftpd and would like to make the package of it, because I > did not find in the ports tree. I can construct it and send to list > for testing? Proftpd entered the ports tree in 1998, and was pulled (finally) in 2002: http://www.openbsd.org/cgi-bin/cvsweb/ports/net/proftpd/Attic/Makefile
Proftpd port
I am using proftpd and would like to make the package of it, because I did not find in the ports tree. I can construct it and send to list for testing? Thks, -- Rafael
Re: Remove x11/ion
* Darrin Chandler <[EMAIL PROTECTED]> [2007-04-30 09:49:19]: > On Mon, Apr 30, 2007 at 11:24:07AM -0500, Marco Peereboom wrote: > > Sure we can keep ion3 ad is but I'd like to pick up the new changes in a > > forked project called bananawm :-) > > bananawm? I don't get it. How about FreeIon for a fork: > > "FreeIon: if you're not part of the solution, you're part of the > precipitate" > Naw, I like bananawm better =). Such features could include: . Changing the mouse cursor to a banana. . A theme song is absolutely necessary... http://en.wikipedia.org/wiki/Bananaphone . Banana background! . Floating bananas like xsnow! . A banana clock... hrm, analog sounds good, but binary or digital would suffice. . A Pulp Fiction themed FPS with the only weapons being bannanas... hey, a wm has to have it all, after all! See http://www.flickr.com/photos/i-capture/16136112/ for an artistic example we can base it off of. Banana, mofo, do you speak it? But in all seriousness, FreeIon sounds good. Little bit easier to figure out just what the hell it is. Anyone serious about sed'ing this port to hell? -- Travers Buda
Re: Update www/sarg
Douglas Santos <[EMAIL PROTECTED]> wrote: > Update sarg-2.1 -> 2.2.3.1 > gd disabled for now. Why is it disabled for now? Alek -- - Chcę zrozumieć wszystko - oświadczył Miro. - Chcę wiedzieć wszystko, a potem zestawić razem i zbadać, co się tam kryje. - Znakomity projekt - przyznała. - Będzie dobrze wyglądał w twoim resume. -- Orson Scott Card, Mówca Umarłych.
UPDATE: devel/py-parsing
The attached diff updates devel/py-parsing from 1.4.4 to 1.4.6, a
bugfix and feature enhancement release. I also add myself as
MAINTAINER.
The updated port tests well on i386/-current. graphics/py-dot, the
only port that depends on py-parsing, also works fine with 1.4.6.
Diff is attached and available via HTTP:
http://www.lfod.us/files/ports/py-parsing.diff
Thanks!
--
o--{ Will Maier }--o
| web:...http://www.lfod.us/ | [EMAIL PROTECTED] |
*--[ BSD Unix: Live Free or Die ]--*
Index: Makefile
===
RCS file: /cvs/ports/devel/py-parsing/Makefile,v
retrieving revision 1.8
diff -u -u -r1.8 Makefile
--- Makefile2006/10/30 10:45:57 1.8
+++ Makefile2007/04/30 17:45:17
@@ -2,11 +2,13 @@
COMMENT= "Python parsing module"
-DISTNAME= pyparsing-1.4.4
+DISTNAME= pyparsing-1.4.6
PKGNAME= ${DISTNAME:S/py/py-/}
CATEGORIES=devel
HOMEPAGE= http://pyparsing.sourceforge.net/
+
+MAINTAINER=Will Maier <[EMAIL PROTECTED]>
# MIT
PERMIT_PACKAGE_CDROM= Yes
Index: distinfo
===
RCS file: /cvs/ports/devel/py-parsing/distinfo,v
retrieving revision 1.8
diff -u -u -r1.8 distinfo
--- distinfo2007/04/05 15:38:05 1.8
+++ distinfo2007/04/30 17:45:17
@@ -1,5 +1,5 @@
-MD5 (pyparsing-1.4.4.tar.gz) = auSL1ScJR1bG5XUmey0bMA==
-RMD160 (pyparsing-1.4.4.tar.gz) = pMHwyjVCEwTPzHUmchEAPV9XC6s=
-SHA1 (pyparsing-1.4.4.tar.gz) = LopOjXed220mRNTmooPx96/9KiU=
-SHA256 (pyparsing-1.4.4.tar.gz) = ZiL98vqBG0F31oEjCyMG65Qo7Hp/1h2U5vmdRt4792E=
-SIZE (pyparsing-1.4.4.tar.gz) = 703894
+MD5 (pyparsing-1.4.6.tar.gz) = 9QT/jLvZqCt596zfNdMO5g==
+RMD160 (pyparsing-1.4.6.tar.gz) = prOq957EPaCjYeZtp0fBVq12res=
+SHA1 (pyparsing-1.4.6.tar.gz) = Iedo2IZ3Wki8zWKQ2nvqYRW/lB8=
+SHA256 (pyparsing-1.4.6.tar.gz) = YIA4etmPumcv5vxH5mpqS8AAojXlw9taHOiV9GD5Lbw=
+SIZE (pyparsing-1.4.6.tar.gz) = 725897
Index: pkg/PLIST
===
RCS file: /cvs/ports/devel/py-parsing/pkg/PLIST,v
retrieving revision 1.7
diff -u -u -r1.7 PLIST
--- pkg/PLIST 2006/10/30 10:45:57 1.7
+++ pkg/PLIST 2007/04/30 17:45:17
@@ -1,6 +1,4 @@
@comment $OpenBSD: PLIST,v 1.7 2006/10/30 10:45:57 xsa Exp $
-lib/python${MODPY_VERSION}/
-lib/python${MODPY_VERSION}/site-packages/
lib/python${MODPY_VERSION}/site-packages/pyparsing.py
lib/python${MODPY_VERSION}/site-packages/pyparsing.pyc
share/doc/py-parsing/
@@ -46,11 +44,9 @@
share/doc/py-parsing/parserFwk.pyparsing.ParseFatalException-class.html
share/doc/py-parsing/parserFwk.pyparsing.ParseResults-class.html
share/doc/py-parsing/parserFwk.pyparsing.ParserElement-class.html
-share/doc/py-parsing/parserFwk.pyparsing.PositionToken-class.html
share/doc/py-parsing/parserFwk.pyparsing.QuotedString-class.html
share/doc/py-parsing/parserFwk.pyparsing.RecursiveGrammarException-class.html
share/doc/py-parsing/parserFwk.pyparsing.Regex-class.html
-share/doc/py-parsing/parserFwk.pyparsing.ReparseException-class.html
share/doc/py-parsing/parserFwk.pyparsing.SkipTo-class.html
share/doc/py-parsing/parserFwk.pyparsing.StringEnd-class.html
share/doc/py-parsing/parserFwk.pyparsing.StringStart-class.html
@@ -71,6 +67,8 @@
share/examples/py-parsing/LAparser.py
share/examples/py-parsing/SimpleCalc.py
share/examples/py-parsing/SingleForm.dfm
+share/examples/py-parsing/adventureEngine.py
+share/examples/py-parsing/cLibHeader.py
share/examples/py-parsing/chemicalFormulas.py
share/examples/py-parsing/commasep.py
share/examples/py-parsing/configParse.py
@@ -85,21 +83,29 @@
share/examples/py-parsing/greeting.py
share/examples/py-parsing/greetingInGreek.py
share/examples/py-parsing/greetingInKorean.py
+share/examples/py-parsing/holaMundo.py
+share/examples/py-parsing/htmlStripper.py
share/examples/py-parsing/httpServerLogParser.py
share/examples/py-parsing/idlParse.py
share/examples/py-parsing/indentedGrammarExample.py
+share/examples/py-parsing/jsonParser.py
share/examples/py-parsing/linenoExample.py
+share/examples/py-parsing/list1.py
share/examples/py-parsing/listAllMatches.py
+share/examples/py-parsing/macroExpander.py
share/examples/py-parsing/makeHTMLTagExample.py
share/examples/py-parsing/mozilla.ics
share/examples/py-parsing/mozillaCalendarParser.py
share/examples/py-parsing/parseListString.py
+share/examples/py-parsing/parsePythonValue.py
share/examples/py-parsing/pgn.py
share/examples/py-parsing/pythonGrammarParser.py
share/examples/py-parsing/removeLineBreaks.py
share/examples/py-parsing/romanNumerals.py
share/examples/py-parsing/scanExamples.py
+share/examples/py-parsing/scanYahoo.py
share/examples/py-parsing/searchparser.py
+share/examples/py-parsing/sexpParser.py
share/examples/py-parsing/simpleArith.py
share/examples/py-parsing/simpleBool.py
share/examples/py-parsing/simpleSQL.py
Re: [+] Re: Remove x11/ion
* Antoine Jacoutot wrote: > On Mon, 30 Apr 2007, Marc Balmer wrote: > >>Then we should just remove the damn software. > > > >No. > > lol, I love the way you argue... heh ;) indeed. the argumentation is in an email I sent some minutes earlier... > > -- > Antoine
Re: [+] Re: Remove x11/ion
* Antoine Jacoutot wrote: > On Monday 30 April 2007 16:55:21 Pedro Martelletto wrote: > > What we could do is to distribute the software under a different name, > > like 'anion'. This way we would not be affected by the restrictions. > > Yeah, I though about it at first, but I found it weird. > I mean, most people will think there's no package for Ion whereas there is. > > > I don't believe talking to the author would help. Besides the fact that > > he was quite firm in his decision, I'm not willing to do that myself. > > +1 > Then we should just remove the damn software. No. > > -- > Antoine >
Re: Remove x11/ion
* Pedro Martelletto wrote: > As can be seen in http://tinyurl.com/2pelmo [1], the author of x11/ion > recently changed the software's license to something obscure, completely > open to misinterpretation, and in my opinion incompatible with our ports > tree. > > Therefore, I'd like to propose the complete removal of the port. There is other software in the ports that has or had obscure licenses. E.g we have Apache 2, we had graphviz etc. The ports tree is here for our users convenience. If a port has a strange license, you can always set the PERMIT_xy fields. Many users use ion, so why should we harrass them? The ports tree is the wrong area to fight license battles, imo. That said, I am obviously against the removal of ion.
Re: Remove x11/ion
On Mon, Apr 30, 2007 at 11:24:07AM -0500, Marco Peereboom wrote: > Sure we can keep ion3 ad is but I'd like to pick up the new changes in a > forked project called bananawm :-) bananawm? I don't get it. How about FreeIon for a fork: "FreeIon: if you're not part of the solution, you're part of the precipitate" -- Darrin Chandler| Phoenix BSD User Group | MetaBUG [EMAIL PROTECTED] | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: Remove x11/ion
On Mon, Apr 30, 2007 at 10:44:50AM -0600, Theo de Raadt wrote: > Actually, it is not a matter of conformance against what the author > believes. Authors believe the most retarded things from time to time. Sure, but it _was_ due to a possible conformance problem that I suggested the removal of the port, and not because I didn't like the license. That's what I wanted to point out. -p.
Re: Remove x11/ion
> On Mon, Apr 30, 2007 at 06:25:21PM +0200, Marc Balmer wrote: > > The ports tree is here for our users convenience. If a port has a > > strange license, you can always set the PERMIT_xy fields. Many users > > use ion, so why should we harrass them? > > It was not a simple question of removing the port because we didn't like > the license. It was a question of conformance, at least towards what the > author believes the rules now are. Actually, it is not a matter of conformance against what the author believes. Authors believe the most retarded things from time to time. The same thing happened with qmail before. djb thought we could have his code in the ports tree, but since he specifically does not copyright his code visibly, no rights are granted, so we could not include it, and had to delete it. It's more about conformance with the laws, than about whatever fantasy the author has.
Re: Remove x11/ion
Please wait, I'm going to talk to Tuomo.
Re: [+] Re: Remove x11/ion
On Mon, 30 Apr 2007, Marc Balmer wrote: Then we should just remove the damn software. No. lol, I love the way you argue... -- Antoine
Re: Remove x11/ion
On Mon, Apr 30, 2007 at 06:25:21PM +0200, Marc Balmer wrote: > The ports tree is here for our users convenience. If a port has a > strange license, you can always set the PERMIT_xy fields. Many users > use ion, so why should we harrass them? It was not a simple question of removing the port because we didn't like the license. It was a question of conformance, at least towards what the author believes the rules now are. > The ports tree is the wrong area to fight license battles, imo. That > said, I am obviously against the removal of ion. That's precisely why I didn't want to fight any. -p.
Re: Remove x11/ion
Sure we can keep ion3 ad is but I'd like to pick up the new changes in a forked project called bananawm :-) On Mon, Apr 30, 2007 at 05:52:04PM +0200, Pedro Martelletto wrote: > On Mon, Apr 30, 2007 at 09:45:37AM -0600, Theo de Raadt wrote: > > I think a better fight against such balony is to keep his code in the > > ports tree under the existing (previous) license, and let it rot at > > that level, if need be. > > > > Once you release something under a copyright, there is no retroactive > > right. That's just not how it works. > > > > Leaving stuff available in some way for people to do forks is a good > > idea, of course. > > Okay, let's do that then. Marco, are you fine with this? > > -p. >
Re: Remove x11/ion
On Mon, Apr 30, 2007 at 09:45:37AM -0600, Theo de Raadt wrote: > I think a better fight against such balony is to keep his code in the > ports tree under the existing (previous) license, and let it rot at > that level, if need be. > > Once you release something under a copyright, there is no retroactive > right. That's just not how it works. > > Leaving stuff available in some way for people to do forks is a good > idea, of course. Okay, let's do that then. Marco, are you fine with this? -p.
Re: Remove x11/ion
> On Mon, Apr 30, 2007 at 10:20:37AM -0500, Travers Buda wrote: > > Point is, the unencumbered port works, no point in removing it over spite. > > http://article.gmane.org/gmane.comp.window-managers.ion.general/7694 > > The author believes the license change to be retroactive (even though > that's clearly not possible). Consequentially, there is no way we can > keep the port without either starting a fight with him (something I > honestly don't have the time or patience to endure) or 'violating' his > restrictions. I think a better fight against such balony is to keep his code in the ports tree under the existing (previous) license, and let it rot at that level, if need be. Once you release something under a copyright, there is no retroactive right. That's just not how it works. Leaving stuff available in some way for people to do forks is a good idea, of course.
x11/dwm (was: Remove x11/ion)
On Tue, May 01, 2007 at 12:07:37AM +1000, Donald Bruce Stewart wrote: > Urgh. Tuomo is weird sometimes. More reasons to move to > > wmii / dwmhttp://www.suckless.org/wiki/dwm (MIT/X) For dwm, see attachment. > xmonad http://xmonad.org/ (BSD3) If this needs a recent ghc, it still has to wait some days (ghc-6.6.1 is work in progress here). Ciao, Kili -- Was soll ich in New York - ich war schon zweimal in Hannover. -- Arno Schmidt (1914-79), dt. Schriftsteller dwm.tgz Description: application/tar-gz
Re: [+] Re: Remove x11/ion
Anion sounds great to me. Please don't kill the port over a name. On Mon, Apr 30, 2007 at 04:55:21PM +0200, Pedro Martelletto wrote: > On Mon, Apr 30, 2007 at 04:17:15PM +0200, Antoine Jacoutot wrote: > > Well, the licence is still LGPL, right? > > Only the use of the name "Ion*" is restricted in a very weird way. > > > > Can't you get in touch with the author to see if this can be fixed in some > > way, something ala firefox? > > What we could do is to distribute the software under a different name, > like 'anion'. This way we would not be affected by the restrictions. > > I don't believe talking to the author would help. Besides the fact that > he was quite firm in his decision, I'm not willing to do that myself. > > -p. >
Re: Remove x11/ion
On Mon, Apr 30, 2007 at 10:20:37AM -0500, Travers Buda wrote: > Point is, the unencumbered port works, no point in removing it over spite. http://article.gmane.org/gmane.comp.window-managers.ion.general/7694 The author believes the license change to be retroactive (even though that's clearly not possible). Consequentially, there is no way we can keep the port without either starting a fight with him (something I honestly don't have the time or patience to endure) or 'violating' his restrictions. -p.
Re: Remove x11/ion
* Pedro Martelletto <[EMAIL PROTECTED]> [2007-04-30 15:58:02]: > As can be seen in http://tinyurl.com/2pelmo [1], the author of x11/ion > recently changed the software's license to something obscure, completely > open to misinterpretation, and in my opinion incompatible with our ports > tree. > > Therefore, I'd like to propose the complete removal of the port. > How about no. We can easily keep around a compatible version; I find ion3 to be quite stable anyhow. Besides, OpenBSD has been known to keep 6 year old WM code around. Point is, the unencumbered port works, no point in removing it over spite. -- Travers Buda
Re: [+] Re: Remove x11/ion
On Monday 30 April 2007 16:55:21 Pedro Martelletto wrote: > What we could do is to distribute the software under a different name, > like 'anion'. This way we would not be affected by the restrictions. Yeah, I though about it at first, but I found it weird. I mean, most people will think there's no package for Ion whereas there is. > I don't believe talking to the author would help. Besides the fact that > he was quite firm in his decision, I'm not willing to do that myself. +1 Then we should just remove the damn software. -- Antoine
Re: [+] Re: Remove x11/ion
On Mon, Apr 30, 2007 at 04:17:15PM +0200, Antoine Jacoutot wrote: > Well, the licence is still LGPL, right? > Only the use of the name "Ion*" is restricted in a very weird way. > > Can't you get in touch with the author to see if this can be fixed in some > way, something ala firefox? What we could do is to distribute the software under a different name, like 'anion'. This way we would not be affected by the restrictions. I don't believe talking to the author would help. Besides the fact that he was quite firm in his decision, I'm not willing to do that myself. -p.
Re: Remove x11/ion
On Monday 30 April 2007 15:58:02 Pedro Martelletto wrote: > As can be seen in http://tinyurl.com/2pelmo [1], the author of x11/ion > recently changed the software's license to something obscure, completely > open to misinterpretation, and in my opinion incompatible with our ports > tree. Well, the licence is still LGPL, right? Only the use of the name "Ion*" is restricted in a very weird way. Can't you get in touch with the author to see if this can be fixed in some way, something ala firefox? > Therefore, I'd like to propose the complete removal of the port. If no solution can be found, then yes, I'd agree with that. -- Antoine
Re: Remove x11/ion
pedro: > As can be seen in http://tinyurl.com/2pelmo [1], the author of x11/ion > recently changed the software's license to something obscure, completely > open to misinterpretation, and in my opinion incompatible with our ports > tree. > > Therefore, I'd like to propose the complete removal of the port. > > -p. > > [1] http://article.gmane.org/gmane.comp.window-managers.ion.general/7701 Urgh. Tuomo is weird sometimes. More reasons to move to wmii / dwmhttp://www.suckless.org/wiki/dwm (MIT/X) or xmonad http://xmonad.org/ (BSD3) -- Don
Remove x11/ion
As can be seen in http://tinyurl.com/2pelmo [1], the author of x11/ion
recently changed the software's license to something obscure, completely
open to misinterpretation, and in my opinion incompatible with our ports
tree.
Therefore, I'd like to propose the complete removal of the port.
-p.
[1] http://article.gmane.org/gmane.comp.window-managers.ion.general/7701
Index: Makefile
===
RCS file: /cvs/ports/x11/Makefile,v
retrieving revision 1.274
diff -u -r1.274 Makefile
--- Makefile11 Apr 2007 16:20:39 - 1.274
+++ Makefile30 Apr 2007 13:49:41 -
@@ -85,7 +85,6 @@
SUBDIR += icewm
SUBDIR += icon-naming-utils
SUBDIR += idesk
- SUBDIR += ion
SUBDIR += itk
SUBDIR += iwidgets
SUBDIR += jmk-fonts
Index: ion/Makefile
===
RCS file: ion/Makefile
diff -N ion/Makefile
--- ion/Makefile25 Apr 2007 09:46:43 - 1.47
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,29 +0,0 @@
-# $OpenBSD: Makefile,v 1.47 2007/04/25 09:46:43 pedro Exp $
-
-COMMENT= "light, keyboard friendly window manager"
-
-V= 20070318
-DISTNAME= ion-3ds-${V}
-PKGNAME= ion-${V}p0
-CATEGORIES=x11
-
-HOMEPAGE= http://modeemi.cs.tut.fi/~tuomov/ion/
-MASTER_SITES= http://modeemi.cs.tut.fi/~tuomov/dl/
-
-MAINTAINER=Pedro Martelletto <[EMAIL PROTECTED]>
-
-# LGPL
-PERMIT_PACKAGE_CDROM= Yes
-PERMIT_PACKAGE_FTP=Yes
-PERMIT_DISTFILES_CDROM=Yes
-PERMIT_DISTFILES_FTP= Yes
-
-WANTLIB= ICE X11 m c SM Xext
-MODULES= devel/gettext
-LIB_DEPENDS= lua.>=5.1::lang/lua
-
-USE_GMAKE= Yes
-USE_X11= Yes
-NO_REGRESS=Yes
-
-.include
Index: ion/distinfo
===
RCS file: ion/distinfo
diff -N ion/distinfo
--- ion/distinfo5 Apr 2007 17:36:22 - 1.25
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,5 +0,0 @@
-MD5 (ion-3ds-20070318.tar.gz) = 8CJkq37MmQws0yL1el6KTQ==
-RMD160 (ion-3ds-20070318.tar.gz) = p8ybrqNiSw7YQP3IL8XbKsEBjZo=
-SHA1 (ion-3ds-20070318.tar.gz) = 81Khx/b0ZUeBQdU4sqTD8+gaTzA=
-SHA256 (ion-3ds-20070318.tar.gz) = cS2gJ/sSd09n2TPZWpVFLZilZYYX/FUVARynm2A1JYo=
-SIZE (ion-3ds-20070318.tar.gz) = 657282
Index: ion/patches/patch-etc_cfg_ioncore_lua
===
RCS file: ion/patches/patch-etc_cfg_ioncore_lua
diff -N ion/patches/patch-etc_cfg_ioncore_lua
--- ion/patches/patch-etc_cfg_ioncore_lua 28 Mar 2007 19:33:04 -
1.6
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,36 +0,0 @@
-$OpenBSD: patch-etc_cfg_ioncore_lua,v 1.6 2007/03/28 19:33:04 pedro Exp $
etc/cfg_ioncore.lua.orig Sun Dec 24 08:45:26 2006
-+++ etc/cfg_ioncore.luaSun Dec 24 08:48:23 2006
-@@ -63,8 +63,8 @@ defbindings("WScreen", {
- kpress(META.."F9", "ioncore.create_ws(_)"),
-
- bdoc("Display the main menu."),
--kpress(ALTMETA.."F12", "mod_query.query_menu(_, _sub, 'mainmenu', 'Main
menu:')"),
----kpress(ALTMETA.."F12", "mod_menu.menu(_, _sub, 'mainmenu',
{big=true})"),
-+--kpress(ALTMETA.."F12", "mod_query.query_menu(_, _sub, 'mainmenu', 'Main
menu:')"),
-+kpress(ALTMETA.."F12", "mod_menu.menu(_, _sub, 'mainmenu', {big=true})"),
- mpress("Button3", "mod_menu.pmenu(_, _sub, 'mainmenu')"),
-
- bdoc("Display the window list menu."),
-@@ -139,10 +139,10 @@ defbindings("WMPlex.toplevel", {
- kpress(META.."T", "WRegion.set_tagged(_sub, 'toggle')", "_sub:non-nil"),
-
- bdoc("Query for manual page to be displayed."),
--kpress(ALTMETA.."F1", "mod_query.query_man(_, ':man')"),
-+kpress(ALTMETA.."F1", "mod_query.query_man(_, '::man')"),
-
- bdoc("Show the Ion manual page."),
--kpress(META.."F1", "ioncore.exec_on(_, ':man ion3')"),
-+kpress(META.."F1", "ioncore.exec_on(_, '::man ion3')"),
-
- bdoc("Run a terminal emulator."),
- kpress(ALTMETA.."F2", "ioncore.exec_on(_, XTERM or 'xterm')"),
-@@ -158,7 +158,7 @@ defbindings("WMPlex.toplevel", {
-
- bdoc("Query for file to edit."),
- kpress(ALTMETA.."F5",
-- "mod_query.query_editfile(_, 'run-mailcap --action=edit')"),
-+ "mod_query.query_editfile(_, ':vi')"),
-
- bdoc("Query for file to view."),
- kpress(ALTMETA.."F6",
Index: ion/patches/patch-mod_statusbar_ion-statusd_statusd_mail_lua
===
RCS file: ion/patches/patch-mod_statusbar_ion-statusd_statusd_mail_lua
diff -N ion/patches/patch-mod_statusbar_ion-statusd_statusd_mail_lua
--- ion/patches/patch-mod_statusbar_ion-statusd_statusd_mail_lua8 Jun
2005 12:45:55 - 1.2
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,12 +0,0 @@
-$OpenBSD: patch-mod_statusbar_ion-statusd_statusd_mail_lua,v 1.2 2005/06/08
12:45:55 pedro Exp $
mod_statusbar/ion-statusd/statusd_mail.lua.origTue Jun
pkg_create changes
I've been doing a lot of small changes to pkg_create, mostly to clean up and unify the code. There should be very little change in behavior, but the internal logic is simpler and more uniform. In particular, various special modes, such as pkg_create -n, or pkg_create -f /var/db/pkg/name/+CONTENTS will perform more sensible checks For instance, all files are now treated the same way, including special stuff like +DISPLAY and friends. Also, in pkg regen mode, pkg_create more or less ignores most options except -f.
Re: NEW: net/wput
On Sat, Apr 28, 2007 at 03:25:26PM +0200, Giovanni Bechis wrote: > pkg/DESCR: > Wput is a command-line ftp-client that looks like wget > but instead of downloading, uploads files or whole directories > to remote ftp-servers. > Tested on i386, ok ? > Added a dependency and disabled -g switch on compiling. The new port could be downloaded from: http://bigio.snb.it/openbsd/wput-0.6.tgz Giovanni
Re: NEW: net/jabberd14
Ingo Schwarze [2007-04-30, 00:24:32]:
> Hi Jasper, hi Steven, hi Wijnand,
>
> i reworked jasper@'s version of the net/jabberd14 port in two
> respects. Hopefully, this is now final...
>
> 1. To clean up the {SYS,J_}CONFDIR havoc, i have
> - added "--sysconfdir=${J_CONFDIR}" to CONFIGURE_ARGS
>to make ${WRKSRC}/Makefile and ${WRKSRC}/config.h happy
> - added "old" to CONFIGURE_STYLE in order to prevent gnu.port.mk
>from appending --sysconfdir=${SYSCONFDIR} to CONFIGURE_ARGS,
>thus overriding my beautiful --sysconfdir=${J_CONFDIR}
>(this idea shamelessly stolen from the mail/mutt port)
> - added "--mandir=${PREFIX}/man" to CONFIGURE_ARGS
>to compensate for a side effect of CONFIGURE_STYLE=old
> - added "SUBST_VARS= J_CONFDIR"
> - changed ${SYSCONFDIR} to ${J_CONFDIR} in ${PKGDIR}/PLIST
>
> 2. To use xenocara expat, i have
> - added "expat" to WANTLIB
> - removed "expat::textproc/expat" from LIB_DEPENDS
> - added "--with-libexpat=/usr/X11R6" to CONFIGURE_ARGS
Use X11BASE here instead of hardcoding /usr/X11R6.
> After that, all four jabberd14 flavors build fine when the
> expat package is not installed.
> When the expat package is installed, the port picks it up,
> ignoring xenocara. No idea how to avoid that while at the
> same time linking against idn, popt and pth. No idea whether
> this is any problem at all. The expat port will go away anyway,
> so nobody ought to have it installed during bulk builds, right?
>
> This is what i kept:
> - Wijnand's patch to detect snprintf by autoconf
> - Jasper's improvements to README.OpenBSD and MESSAGE
>
> Please cross-check once more and commit.
Let's try to improve it some more first.
- If I use sudo -u _jabberd14 /usr/local/bin/jabberd14 -D
I see an error occurring here:
Mon Apr 30 09:09:11 2007 log.c:232 could not open directory
/var/spool/jabberd/inject.localhost for reading
- It would be less confusing if you modify the jabber.xml config file with
the defaults you mention in README.OpenBSD, e.g. user/database for mysql.
If you use wrong credentials here, jabberd14 terminates with a
segmentation fault if you try to register a new user (at least on amd64).
- Maybe it would be good to have it use /var/run/jabberd14/ instead of
/var/run/jabberd/ ? especially if this is used by the other jabberd
port, I haven't checked.
- Use J_CONFDIR in README.OpenBSD as well
- Use PREFIX instead of LOCALBASE in MESSAGE
- In this line in README.OpenBSD, you want to drop the '>'
$ mysql -u jabberd14 -p jabberd14 \
> < /usr/local/share/examples/jabberd14/mysql.sql
- A segmentation fault also occurs when pressing ^C a couple of times
(when it's running in the foreground, amd64), trace below
#0 _xhasher (s=0x409d426b ) at xhash.c:64
#1 0x4e5c5e33 in xhash_zap (h=0x482be000,
key=0x409d426b ) at xhash.c:276
#2 0x4e5c5c23 in _xhash_cleaner_walk (hash=0x409d426b,
key=0x409d426b , value=0x49899aa0,
arg=0x0) at xhash.c:129
#3 0x4e5c5f30 in xhash_walk (h=0x482be000,
w=0x4e5c5c10 <_xhash_cleaner_walk>, arg=0x0) at xhash.c:332
#4 0x4e5c5c47 in _xhash_cleaner (arg=0x409d426b) at xhash.c:146
#5 0x4e5c72ec in pool_free (p=0x4073e320) at pool.c:411
#6 0x4e5c5eb1 in xhash_free (h=0x409d426b) at xhash.c:308
#7 0x4e5c2c29 in deliver_shutdown () at deliver.c:680
#8 0x00404fc9 in _jabberd_atexit () at jabberd.cc:463
#9 0x4d109da9 in exit (status=0) at
/usr/src/lib/libc/stdlib/exit.c:61
#10 0x00404f4c in _jabberd_shutdown () at jabberd.cc:435
#11 0x0040503d in jabberd_signal_handler (arg=0x409d426b)
at jabberd.cc:509
#12 0x4e5bce4f in heartbeat (arg=0x409d426b) at heartbeat.c:82
#13 0x462b182b in pth_spawn_trampoline ()
from /usr/local/lib/libpth.so.20.25
...
steven
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
