hi, there!

08 Jan 03 11:53, Gerrit Kuehn wrote to Max Khon:

 MK>> By the way I have just committed FreeBSD ports for the following
 MK>> Husky Fidosoft Project modules (I have taken latest -stable release
 MK>> from sourceforge):

 GK> Hm, we should have coordinated our efforts. I'm also creating FreeBSD 
 GK> ports for Husky, but they're not all finished yet. :)
 GK> Can you send me your ports for trying out?

I have already committed them. Just update your ports collections
(all of them are in news husky-xxx)

 MK>> Packages should appear on ftp.freebsd.org and mirrors within a few 
 MK>> days
 MK>> (after next successful full package run on package building cluster)
 MK>> if there will be no errors in ports I created (if I didn't miss 
 MK>> something).

 GK> I doubt that. The complete ports tree is still in freeze because of 
 GK> the upcoming 5.0-Release (for several weeks now). I havn't seen your 
 GK> commits on
 GK> freebsd-ports mailing list until now, either. How did you commit?

ports tree is was unfrozen about two weeks ago.
You can finds the ports in cvsweb:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/news/

cvs log message is here:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=146920+0+current/cvs-all

 MK>> I plan to maintain these ports in future and I wonder whether there 
 MK>> exists
 MK>> some mailing list on which announcements are made about new stable
 MK>> releases of Husky Fidosoft Project modules?

 GK> Actually this echo should be the platform to announce new releases.

 MK>> The last question is why source-only tarballs that are distributed 
 MK>> from
 MK>> sourceforge have such strange version naming?

 GK> I already wondered about that, too. ;-)

 MK>> What is the number after hyphen in package version?
 MK>> This additional number conflicts a bit with FreeBSD package naming
 MK>> (and with scheme that is used for .rpm-based Linux distributions).

 GK> Did you use WRKSRC to overcome this problem, or how did you solve it?

I did use WRKSRC (there is no problem with it). The problem is that
portlint complains about hyphens in version number and I had to use
PORTREVISION. Changes in port still can be tracked using PORTEPOCH
but using PORTREVISION for keeping part of PORTVERSION is not good.

/fjoe

--- Msged/BSD 6.0.1