Please repocopy irc/ircd-ratbox-devel (3.0.7) over to irc/ircd-ratbox
to replace the deprecated version.
The supplied patch should:
- Make the necessary changes to convert the "devel" port into the "stable" one.
- Avoid listing Perl as a dependency when it is not required.
- Remove some @unexec usage in pkg-plist.
--- Note for /usr/src/UPDATING ---
ircd-ratbox has been updated to follow the current stable release branch (3.0.x).
All previous branches are no longer supported by the ratbox team.
Users of ircd-ratbox are advised to create new ircd configuration files based on
the examples provided.
--- End of note ---
I'll take it. I got 166914 also.
Waiting on pr 166914 to close
pr 166914 comitted. Please repocopy
pr 166914 comitted. Please repocopy
do you want -devel deleted from ports tree with repocopy? or leave it?
You want to write a MOVED entry? or should I ?
Michael Scheidell, CTO
>*| * SECNAP Network Security Corporation
Sorry, I used bad terminology... At the time I thought repocopy was a
euphemism for "updating or syncing one port's current files with
another", but have come to understand that it is certainly not. I
definitely don't wish for the ports to be repocopied, sorry for the
To clarify; the "-devel" release of ircd-ratbox is now considered
stable, meaning there is currently no development version available.
I've updated irc/ircd-ratbox-devel to the most recent release and meant
to ask if the two ports could please be synchronised, such that the
deprecated (old "stable") version of the port is updated to the current
release branch (by copying irc/ircd-ratbox-devel files over
irc/ircd-ratbox and then applying the supplied patch).
scheidell 2012-04-15 10:52:14 UTC
FreeBSD ports repository
irc/ircd-ratbox Makefile distinfo pkg-descr pkg-plist
- Major release update to 3.0.7. Read /usr/ports/UPDATING
Submitted by: moggie <email@example.com> (maintainer)
Reviewed by: scheidell (me)
Revision Changes Path
1.1219 +11 -1 ports/UPDATING
1.20 +65 -32 ports/irc/ircd-ratbox/Makefile
1.11 +2 -2 ports/irc/ircd-ratbox/distinfo
1.2 +0 -11 ports/irc/ircd-ratbox/files/patch-Makefile.in (dead)
1.3 +0 -11 ports/irc/ircd-ratbox/files/patch-contrib_Makefile.in (dead)
1.2 +2 -2 ports/irc/ircd-ratbox/files/patch-contrib_ircd-shortcut.pl
1.2 +10 -15 ports/irc/ircd-ratbox/files/patch-doc_Makefile.in
1.4 +33 -16 ports/irc/ircd-ratbox/files/patch-doc_example.conf
1.4 +36 -19 ports/irc/ircd-ratbox/files/patch-doc_example.efnet.conf
1.2 +0 -17 ports/irc/ircd-ratbox/files/patch-help_Makefile.in (dead)
1.2 +13 -10 ports/irc/ircd-ratbox/files/patch-include_config.h
1.2 +0 -16 ports/irc/ircd-ratbox/files/patch-modules_Makefile.in (dead)
1.2 +0 -12 ports/irc/ircd-ratbox/files/patch-servlink_Makefile.in (dead)
1.2 +0 -12 ports/irc/ircd-ratbox/files/patch-src_Makefile.in (dead)
1.2 +0 -12 ports/irc/ircd-ratbox/files/patch-tools_Makefile.in (dead)
1.3 +15 -7 ports/irc/ircd-ratbox/files/pkg-install.in
1.5 +19 -4 ports/irc/ircd-ratbox/files/pkg-message.in
1.2 +12 -0 ports/irc/ircd-ratbox/pkg-descr
1.6 +112 -102 ports/irc/ircd-ratbox/pkg-plist
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "email@example.com"
note: next time, supply a patch to ircd-ratware that updates it to tne next version.
(cd ../ircd-ratware. manually everything but CVS files.
cd ./irc rsync -avC ./ircd-ratware-devel ./ircd-ratware
edit ./irc/Makefile and remove ircd-ratware-devel entry if you want it removed.
Q: Did you want ../irc/ircd-ratware-devel removed? and entry made in /usr/ports/MOVED or will you be continuting to use it
for new devel versions? ie: do you want to maintain two versions?
Thanks for sorting this out.
Making a patch to update irc/ircd-ratbox did cross my mind, but I
recalled someone telling me once that patches aren't always the best way
of achieving things like this - as it tends to produce large /
complicated patch files. However, if that is what committers prefer,
I'll be sure to just use a patch next time.
Please leave irc/ircd-ratbox-devel unchanged. I know people actively use
it and at some point in the future I'm sure there will be new testing
Yes, sometimes its complicated. but without it, we could mis-undserstand
exactly what you want. Committed. Thanks!