summaryrefslogtreecommitdiff
path: root/chat
AgeCommit message (Collapse)AuthorFilesLines
2005-05-27Changes 2.2.6:adam5-27/+35
- internal libgadu now work with gnutls instead openssl library. - fixed crash while start. - Tlen.pl configuration moved to .gg2/tlen file - Then to Everaldo www.everaldo.com for his Jabber icons. - close bugs #177,#146,#170,#141,#148 - fixes of parsing links in chat window - and others.
2005-05-25Add RMD160 checksum.wiz1-1/+2
2005-05-24Update to 2.0.8, lots of bugs were fixed. Looks like they stoppedxtraeme5-41/+25
updating the Changelog file for changes (why??).
2005-05-24Added RCS Id to patch-ac.rillig2-2/+4
2005-05-24Replaced empty do-build target with NO_BUILD=yes.rillig1-3/+2
2005-05-24Removed an empty line.rillig3-6/+3
2005-05-23Cleaned up the variable definitions for CFLAGS, LDFLAGS and CONFIGURE_ARGS.rillig1-8/+7
2005-05-23Removed empty line. Fixed MASTER_SITES definition.rillig1-3/+2
2005-05-23Removed unnecessary ${.CURDIR}.rillig2-4/+4
2005-05-23Moved WRKSRC some lines down. Replaced $f with ${f}.rillig1-3/+3
2005-05-23Removed trailing empty line.rillig2-4/+3
2005-05-23Replaced $f with ${f}.rillig1-3/+3
2005-05-23Removed trailing empty line. Set NO_CONFIGURE=yes instead of #defined.rillig1-3/+2
2005-05-23Removed trailing white-space.rillig1-3/+3
2005-05-23Removed trailing white-space.rillig7-13/+13
2005-05-22Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:jlam29-61/+58
USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-05-20On second thought, replacing @..@ with ${..} sounds more like ajlam1-2/+3
"configure" step than a "build" step.
2005-05-20Replace extravagent use of SUBST_CLASSES with one-liner to build thejlam1-10/+4
cgiirc.conf file.
2005-05-18Remove gnome1 packages except as needed for gnucash.wiz10-320/+1
Ok'd by jmmv@ and rh@ (gnome 1 maintainers).
2005-05-16Back out last change. ./ is not correct, but this is a workaround due tooveego2-8/+8
the overwritting of DIST_SUBDIR in the Makefile.
2005-05-15It is ymessenger-0.93.0-1.i386.rpm and not ./ymessenger-0.93.0-1.i386.rpmveego1-4/+4
2005-05-15It is aim-1.5.286-1.i386.rpm and not ./aim-1.5.286-1.i386.rpmveego1-4/+4
2005-05-12Fixed the patch for stripping debugging flags.rillig2-6/+5
2005-05-12Update to version 1.3.0salo4-9/+11
Changes: - Fixes for two remotely exploitable crash bugs. See http://gaim.sourceforge.net/security/ for more information. - Removed parts of the font selection dialog that were not respected - Fix being invited to a multi user chat on MSN - Multiple SILC accounts should work now (Pekka Riikonen) - Fix times on jabber chat backlogs - Fix gevolution plugin to compile with e-d-s 1.0 or 1.2 - Fix gevolution plugin to remember buddy name when someone added you and you then add them - Formatting in jabber chats works - Fix to prevent MSN disconnecting if you change status while - connecting - Change to correctly handle adding jabber buddies on ejabberd servers Mostly from MAINTAINER via PR pkg/30204
2005-05-12Added some patches that are needed to compile on NetBSD-1.6.2/i386.rillig5-1/+78
2005-05-03Sort.wiz1-5/+5
2005-05-02RCD_SCRIPTS_EXAMPLEDIR is no longer customizable.reed10-10/+25
And always is defined as share/examples/rc.d which was the default before. This rc.d scripts are not automatically added to PLISTs now also. So add to each corresponding PLIST as required. This was discussed on tech-pkg in late January and late April. Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
2005-04-28Update to 0.11.7.3:wiz2-7/+6
0.11.7.3: A serious bug in naim's HTML rendering engine has been identified and corrected. Additionally, changes to the packaging have reduced the source tarball size from 529 kB in 0.11.7.2 to 452 kB for 0.11.7.3. naim now completely passes "make distcheck", and distcheck is used to create source tarballs. FireTalk now allows you to send messages to the :RAW target before signing on, to allow passwords to be sent to the server during signon. The IRC driver now handles /names replies from servers that use non-standard status identifiers (such as those who implement "halfop" and other statuses). The UI includes code to suppress duplicate messages and redundant message targets. The embedded Libtool was upgraded to match the stock 1.5.10 release. A new "proto_user_onlineval" chain was added to allow module authors to track buddy online status. 0.11.7.3.1: On some systems, naim's build system was unable to generate a list of special characters to read, which caused naim to interpret the Home key as Ŋ, etc. naim's build system has been changed to work around the issue. No other changes have been made since 0.11.7.3.
2005-04-21Changes 0.4.0:adam5-36/+177
* Easily configured notifications * New icon set * Integration with web browsers * Wizard * Picture transfer * Better voice support * New modules
2005-04-21Changes 1.6rc1:adam5-24/+36
* Fixed: memory leaks, crashes * Now works with a proxy * Enhanced scripts * Bug fixes
2005-04-16update to bsflite-0.80recht3-8/+12
patch by Evan Hall in PR 29964 (slightly modified) 0.80 - 04/13/2005 * Changed keepalive messages to FLAP channel 0x05 messages, as recommended. * Re-implemented idle time reporting. Any keystroke in bsflite now resets your idle time, rather than only on sending a message. * New option "respond_idle_only" to send away message auto-response only when away and idle. * Fixed the terminal line erasing problem previously detailed in the README both in UNIX (using vt100 sequences), Windows (using console functions) and DOS (using conio functions). Plan 9 is unaffected since the rio terminal properly supports reverse line wrap. * Screen names longer than 16 characters are trimmed to the first 13 characters plus "..." in the buddy list display. Use 'wf' to see the entire name. This is necessary now with @mac.com and @thematrixonline.com accounts. * New command 'G' : write away messages in ~/.bsflite/awaymessages, one per line, and use 'G' to set them. * Finally added server-side buddy lists. Buddy add/delete now stores the information on the server. If you have a buddies file, run this new version with it once, then delete it. * Optional "netspeak cleaner" - see cleaner.c and config file * Cleaned up and sped up login sequence. * Fixed a mysterious bug where mobile users would disappear from the buddy list even though they were online. * imcomm now supports sending more than one packet at a time, which seems to be how other clients do some things. The fetch awaymsg/profile command now takes advantage of this, which seems to improve the rate limit situation a bit. Also, the 'b' command works most of the time without triggering a rate limit warning. * Buddy list display now adjusts with screen size. * Added a configuration file. See config-example for details. * Changed default paths to ~/.bsflite/[config,log,profile,buddies,icon] * Fixed the endlessly repeating error messages on certain platforms. * l command now shows the last 20 lines instead of 10. * Implemented MD5-based login in IMComm instead of the old, "roasted" password algorithm. This improves things on three fronts: - your password is no longer sent in plaintext - you can login with a @mac.com account - you can login with an ICQ UIN This is the way the official client has done things for a while. I used MD5 routines developed by L. Peter Deutsch (md5.c, md5.h in imcomm/) for this, at least until I become inspired enough to write my own.
2005-04-16Add buildlink3.mk back, needed by packages in pkgsrc-wip.salo1-0/+21
Bump BUILDLINK_RECOMMENDED. Noticed by <wiz>
2005-04-13Added some patches for ISO C90 compliance. Approved by jlam.rillig4-7/+69
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv81-163/+81
2005-04-11add patch-ab.nathanw1-1/+2
2005-04-11Unmix code and declarations, to placate c89 compilers.nathanw1-0/+21
(Patch submitted upstream)
2005-04-08Sync with the latest silc-client.salo2-7/+7
2005-04-08Update to version 1.0.2salo8-109/+58
Changes: - convert to options.mk 1.0.2: ====== Due to the new SILC Server release with support to the UTF-8 nicknames and channel names new version of the SILC Client is released as it seems the older ones do not function very well with the new server. This version includes support to the UTF-8 encoded nicknames and channel names, however, certain problems may still exists, as this is a slight premature release. - Added support for UTF-8 encoded nicknames and channel names. - Command queue implemented for better UTF-8 support. - --with-silc-includes and --with-silc-libs added gto configure to use pre-installed SILC Toolkit.
2005-04-08Update to version 0.9.19p1salo7-102/+25
Changes: - convert to options.mk 0.9.19p1: ========= A little update with this 0.9.19p1. After such a major release problems were expected and the p1 fixes some crashes. Upgrade strongly recommended. 0.9.19: ======= And after a long break new SILC Server is out. This version finalizes the SILC protocol version 1.2 development and introduces UTF-8 nicknames, channel names, usernames and host names. It is now possible to create practically any kind of nicknames and channel names. Practically all letters, numbers and punctuation marks are supported. Special characters, control characters and various odd symbol characters however are not allowed. Several minor and major bugs has been fixed as well. Upgrading is strongly recommended. Old clients that does not yet support UTF-8 encoded nicknames and channel names are still able to connect and function normally as long as they do not need to handle odd UTF-8 encoded names. - Added support for UTF-8 encoded identifier strings, such as nicknames and channel names. - Fixed founder mode handling on JOIN on normal/backup on empty channels. - Fixed WATCH command handling on backup router. - Fixed WATCH command announcing. The WATCH and SILC Gaim buddy list should work better now. - Simplified INVITE and BAN string handling in server. Announcing INVITE and BAN strings should work more reliably now. - Fixed several bugs from the backup and resuming protocol. - Fixed, hopefully, all the wrong server statistics numbers. - Fixed CLOSE command to handle backup routers correctly. - Fixed various detaching and resuming bugs. - Fixed announcing to not announce unregistered (ghost) clients. - Fixed reconnect_keep_trying and QoS settings in server config files. - Several other bugfixes were made.
2005-04-05Update to 4.20.0, provided by Znarf Ainav on tech-pkg:wiz5-41/+35
4.14.0 ------ Because of the mistake I made in the previous version, the 'u' letter was eaten by the RTF parser when processing messages from windows icq clients. It looked for unicode chars, but ate all 'u' characters it used to found. Fixed that. A memory leak problem when checking RSS was fixed. Gadu-Gadu module used to produce a segfault when it was unable to obtain a registration token from the server. Now it doesn't crash, though the impossibility to register a new UIN is still there. The serve simply doesn't find an appropriate document by the registration URL. Too bad. Applied a small patch by Paul Chitescu so that it's now possible to start centericq with all protocols set to offline. Another type of external event was added. Now you can execute your actions when someone goes offline. Hope someone finds that useful. 4.20.0 ------ PGP encryption support was implemented for the Jabber module. In a nutshell this means that with a proper setup your communications get a way more secure. GPGME library is needed to build the PGP support. Fixed the RTF parser that takes charge when a message from a Windows ICQ client is received. One problem was that it used to treat backspace characters wrong sometimes. Another problem with utf-16 was fixed with a patch submitted by Vadim Nosovsky. After ICQ dual login detection centericq used to try re-connecting, though it wasn't supposed to. Fixed. During a long time noone reported me the bug related to libicq2000's header files getting installed each time "make install" was run for centericq. Finally Wolfram Schlich noted this one, so I fixed it. Logging on Yahoo! didn't work on Sun Sparc machines. Fixed that. That might also revive Gadu-Gadu on bigendian architectures. A couple of interface related bugs were fixed, such as a mistake in the group organization dialog as well as not clearing pending messages for contacts in non-chat communication mode.
2005-04-05Bump BUILDLINK_RECOMMENDED.salo1-2/+2
2005-04-05Update to version 1.2.1salo4-38/+9
Security fixes for three DoS vulnerabilities: Remote DoS on receiving malformed HTML Remote DoS on receiving certain messages over IRC Jabber remote crash Changes: - URL escaping now works with UTF-8 text. This may break some old log files. - Revert to XOR auth for ICQ as the md5 is not fully functional - Fix bug with going away while in a jabber chat - MSN bug fixes (Felipe Contreras) - Escape things properly in IRC From MAINTAINER via PR pkg/29888
2005-04-04Update to latest tarball dated 20050313. About two years (or more)wiz3-457/+615
of undocumented changes.
2005-04-04Update to 2.2. Changes:wiz3-12/+20
EPIC4-2.2 *** News -- 11/09/2004 -- Changes to way spaces are handled *** IMPORTANT *** Up until this point, the technical definition of what is a "space" (the term used for an Internal Field Separator (IFS), that is, the thing that separates one word from another word) EPIC has always had three sets of IFSs 1) Character 32 only ("space") 2) Characters 9, 10, 11, 12, 13, and 32 ("my_isspace()") 3) Whatever your locale says is a space ("isspace") In the C locale (the default for unix users), sets #2 and #3 are exactly the same. I don't know about other locales. Now we are going to only use set #3. Changing Set #2 to Set #3 is easy, and nobody should notice any difference there. The one that is going to cause pain is Set #1. Consider this situation: One<tab>Two Is this one word, or two words? In some places in epic, it is one word, and in other places it is two words. As a result of this change, it will now always be two words every place. Here is a list of the places that were using Set #1 that will change to use Set #3, and you should be on the lookout for changes! *) /AWAY separated the end of its flags with spaces. This means /AWAY -ALL<tab>Hi there! will now work properly. *) $pop(....) removes the last word from the argument list. Whereas $pop(one two<tab>three) used to return "two<tab>three" is will now only return "three" *) Commands are separated from the argument list by a "space". Whereas /one<tab>two blah blah blah parsed "one<tab>two" as the command, now "one" is the command and "two" is part of the argument list. *) In expressions, a variable name may be separated from an operator with a space. Whereas things like @var<tab> =foo might have failed because <tab> is not a valid character in a variable name, it will now treat <tab> the same as a space. *) Places that expect a number did not accept a string that contained a <tab> so that things like <tab><tab>9 was not accepted as a number. Now it will be. *) The /IGNORE command used to consider a string containing a <tab> to not be empty. This means that /IGNORE <tab> would not list the ignorance list, but rather would try to show the ban value for an ignore matching <tab> which isn't reasonable. *) The % wildcard pattern stopped matching only when it saw char 32. Now it will stop whenever it seems a Set 3 type space. So whereas before "%" matched "one<tab>two" now it won't, because "one<tab>two" is two words, not one word. *) In /xdebug extractw mode, tabs before or after double quotes were not considered to start or end a double quoted word. So previously this string: one <tab>"two three" four contained four words, because the <tab> before "two nullified the double quoting. Now that <tab> is treated like any other space, the above word has three words, not four. Places that use Set 1 and will NOT be changing to Set 3, because they are parsing IRC protocol data, which stipulates that the IFS MUST be a space solely: *) CTCP requests and replies are formatted only with spaces *) Words in protocol messages are separated only with spaces *** News -- 11/09/2004 -- You may now mangle ALT_CHAR characters And ALT_CHAR mangling is included in ALL. This was an oversight that was fixed in epic5. *** News -- 11/02/2004 -- Mangling "ALL,-BOLD" no longer mangles "ALL_OFF" In general, if you use ANSI (ALL includes ANSI), the mangled string has its six attributes (COLOR, REVERSE, UNDERLINE, BOLD, BLINK, ALT_CHAR) rewritten into canonical form. This will add some ALL_OFFs to your string that weren't there originally. So if you strip all of the attributes (as ALL does), then epic will strip ALL_OFF off as well. This retains backwards compatability with ALL. But if you use ANSI and don't want to strip all 6 of the attributes, then it's important that ALL_OFFs are not removed, otherwise your string will not appear as it should (the ANSInator uses ALL_OFFs to turn off attributes). So EPIC automatically will not strip ALL_OFFs if you use ANSI and do not mangle one of the 6 attributes. Examples: $stripcrap(ALL this is ^B^_bold underline^_ not bold) will strip everything as it has always done. $stripcrap(ALL,-BOLD this is ^B^_bold underline^_^B not bold) will strip everything but not bold and all_offs, because if all_offs are stripped, then "not bold" will be in bold! The entire point of this is to allow /set mangle_logfile ALL to work the way it has always worked, and $stripcrap(ALL,-BOLD ...) to work the way it *should* work. *** News -- 10/06/2004 -- Support for +e and +I numerics from efnet EFNet has +e and +I channel modes, which act like +b does. These numerics are now handled by epic like +b is. *** News -- 10/06/2004 -- New status bar expandos, %{2}W and %{3}W These two new expandos expand to the same value as %W. %W Expands on each input window on each screen that has two or more visible windows. %{2}W Expands on all visible windows on all screens. %{3}W Expands on each input window on each screen, even on screens that have only one visible window. *** News -- 10/06/2004 -- Support for ircnet's "numeric nick" feature On ircnet, each user is given a unique numeric identifier, which is their one true nickname. In addition to this numeric id, they can have a rfc1459 nickname, but they are not required to have one. Further, the special numeric id 0 is reserved and refers to the user's own numeric id. EPIC now fully supports all of this, particularly in the following ways: /NICK <unique id> /NICK 0 To turn off your rfc1459 nickname. $serverctl(GET <refnum> UNIQUE_ID) $serverctl(SET <refnum> UNIQUE_ID) To retrieve and change your unique nickname. Changing your unique id is probably a bad idea. /USERHOST <unique id> You may USERHOST unique id's now. 'epic 0' You may now use the nickname 0 on the epic command line if you don't want to use an rfc1459 nickname on an ircnet server. Using unique numeric id's on non-ircnet servers is probably fraught with peril. Try to avoid that. *** News -- 10/06/2004 -- /SET INDENT maxes out at 1/3 screen width Previously, if you did /set indent on, and the width of the first word on the first line was > 1/3 of the screen's width, then the second (and subsequent) lines were not indented at all. This was the historical ircII behavior. It seems more sensible to cap the indent level at 1/3 of the screen's width and indent it to there. EPIC4-2.0 *** News -- 02/03/2004 -- ERASE_LINE behavior slightly modified The ERASE_LINE input function has been modified to not overwrite the input buffer when it is called on an empty input line. EPIC4-1.2.9 *** News -- 01/25/2004 -- Slight changes to /ON SSL_SERVER_CERT |Rain| pointed out that /ON SSL_SERVER_CERT was not terribly useful because $1 (cert subject) and $2 (cert issuer) could contain spaces, and so you couldn't really use $1 and $2 to fetch them. He proposed that we hook a url-encoded version of the subject and issuer (so they won't contain any spaces) and you can use $urldecode($1) to get the subject and $urldecode($2) to get the issuer. EPIC4-1.2.7 *** News -- 01/18/2004 -- New functions $cofilter() and $corfilter(). These are compliments of $copattern(). *** News -- 12/27/2003 -- New $dccctl() modes. Added $dccctl(get [ref] writable) and $dccctl(writables). This is useful for sending lots of data out on a raw or chat dcc. Epic will (iirc) normally drop the data in such cases rather than blocking or buffering. This isn't a complete solution. Writable means that a certain amount of data can be written, so data can still be lost. *** News -- 12/27/2003 -- Added /SET DCC_DEQUOTE_FILENAMES This turns the double quoted space decoding feature added recently for received DCC SEND requests on and off. *** News -- 12/27/2003 -- $rest() also removes chars from the right. Using a negative first arg causes $rest() to strip chars from the right hand side of the string. This makes it a compliment to $right() as well as $left(), but if a script relies on it returning the original string the way it did before, it may now cause compatibility problems. If it does, talk to CrazyEddy on #epic efnet. *** News -- 12/27/2003 -- Added $splicec() in functions script. This works much the same way as $splice(), but on characters, not words. It won't work seemlessly on local vars though. EPIC4-1.2.5 *** News -- 12/13/2003 -- Default of AUTO_REJOIN is now OFF Per the poll taken on the epic mailing list, the preponderance of opinion being in favor of changing the default value of AUTO_REJOIN to OFF, as of commit 672, the default value is changed. You will want to put /SET AUTO_REJOIN ON in your ~/.epicrc to get the old value. *** News -- 12/11/2003 -- Command parser ignores spaces after semicolons Since the dawn of the modern ircII syntax, the following syntax has caused consternation with scripters: /eval {two; three} because it runs the /two alias, and then outputs the text "three" to the current target (channel-or-query). This is because the command parser does not ignore spaces after semicolons; a leading space results in ircII assuming you are wanting to run the empty command (yes, there is actually an empty command), which just happens to be the /say command. Well, enough is enough. I'm putting a stop to this. If you depend on this horrifically broken behavior, then the time has come to switch to using /SAY. The rest of us will enjoy not having to freak out about spaces after semicolons. *** News -- 12/11/2003 -- New /WINDOW verb, /WINDOW SCROLLADJ [ON|OFF] When the default value of ON is used, when you "GROW" a window, or otherwise cause the size of a window to be increased, the top of the scrollable view is moved back so you can see more of the lines that have recently scrolled off the screen. If you change this to OFF, the behavior is more like ircII, where when something scrolls off the window, nothing will bring it back unless you go into scrollback mode. *** News -- 12/11/2003 -- New /ON, /ON WINDOW_BEFOREKILL The value of $* is the window refnum (number) of the window that is about to be killed. You cannot stop the kill from happening, but you do get this opportunity to save any information about the window that you might want. *DANGER*DANGER*DANGER* EPIC does not try to stop you from doing something really dumb in this /ON, and if you try to change the window being killed, or you affect the visibility or invisibility of any window, you run the definite chance of confusing EPIC and causing a panic. This is not a bug, this is just your peril if you ignore this warning. Use /DEFER to run commands safely from within /ONs. EPIC4-1.2.3 *** News -- 12/05/2003 -- New built in function $numlines() (fudd) The first argument to $numlines() is the width of a line (which you can get from $geom() if you want to use that), and the rest of the text is some text. The return value is the number of screen lines that will be taken up if you were to /echo the text to a window of the given number of columns. *** News -- 12/03/2003 -- New command line arguments, -o and -O POSIX termios allowed systems to define "extended characters" (IEXTEN) which are interpreted by the kernel and are not passed onto the application. In 4.4BSD in particular, these "extended characters" are ^V and ^O. This means that by default, you cannot use these two characters in a binding. By using the -o option, you ask EPIC to specifically turn these extended characters on, and by using the -O option, you ask epic to specifically turn these extended characters OFF. If you do not specify either option, epic does not change the current default value. EPIC4-1.2.2 *** News -- 12/03/2003 -- New /WINDOW verb, /WINDOW SWAPPABLE [ON|OFF] You may now control whether your windows are "swappable". The default (backwards-compatable) value is ON. If you set this to OFF on a visible window, then that visible window cannot be made hidden, via /WINDOW HIDE or /WINDOW SWAP. If you set this to OFF on a hidden window, then that hidden window cannot be made visible, via /WINDOW SHOW, /WINDOW SWAP, /WINDOW BACK or /WINDOW NEXT. You must reset this value back to ON before you try to swap the window back in or out. *** News -- 12/03/2003 -- New /SET, /SET STATUS_NOSWAP Whenever a window has /WINDOW SWAPPABLE OFF, the %{1}W status expando will expand to the value of this /SET *** News -- 12/03/2003 -- SWAPPABLE accessable via $windowctl() You can now $windowctl(GET <refnum> SWAPPABLE) to get the window <refnum>'s current swappable status.
2005-04-04Changes 2.2.5:adam12-277/+51
* Support for Perl scripts is turned off * Support for skins compatible with Gadu-Gadu * Fixes and stabilisation of the code for status changes * Fixes in tlen.pl plug-in * Now builds basic modules on MacOSX * Improvements of "dockapp" plug-in
2005-04-03Update to version 1.5.286. It's hard to say what changed since 1.5.277fredb2-9/+13
exactly, but 1.5.277 is no longer available on the website. There are no readily apparent functional changes.
2005-04-03- Note import of dircproxy-devel branchadrianp1-1/+2
2005-04-03- Import of the 1.1.x dircproxy devel branchadrianp7-0/+107
dircproxy is an IRC proxy server ("bouncer") designed for people who use IRC from lots of different workstations or clients, but wish to remain connected and see what they missed while they were away. You connect to IRC through dircproxy, and it keeps you connected to the server, even after you detach your client from it. While you're detached, it logs channel and private messages as well as important events, and when you re-attach it'll let you know what you missed. This can be used to give you roughly the same functionality as using ircII and screen together, except you can use whatever IRC client you like, including X ones! * THIS IS AN UNSTABLE DEVELOPMENT RELEASE OF DIRCPROXY. IT HAS HIGHER * THEN USUAL RISK OF DESTROYING YOUR SYSTEM. * * FOR A STABLE RELEASE USE THE LATEST 1.0.x
2005-04-03- Add CONFLICTS for the upcoming import of dircproxy-devel which is the 1.1.xadrianp1-1/+3
branch.
2005-04-02We need to explicitly set PKGNAME to work around a problem in xemacs' ↵jwise1-1/+2
Makefile.pkg.