Hello Max.

08 Jan 03 14:44, you wrote to all:

 MK> (this message was originally posted to husky-discuss{at} but people
 MK> pointed me to this echoarea)

 MK> Most husky modules install man pages, .html and .info files
 MK> using `install' without any arguments. As a result installed files have
 MK> x ('execute') bit set in permissions.
 MK> Will this be fixed?
 MK> I can provide patches for most modules that are published on sourceforge.

Make pathes and send to me please (over fidonet or email:g%ural.org in
binary/uuencoded form)

Good idea is are construct makefiles like one template, for example see
husky-current fidoconf/doc/Makefile or fidoconf/doc/makefile.unx:

INFODIR = /usr/local/info
IMOPT   = -m 644
....
    install $(IMOPT) fidoconfig.info ${INFODIR}


 MK> Another question is: will huskybse and msged be distributed via
 MK> sourceforge any time soon?

Yes. But these modules don't changed in -stable branch and updated only in
-current branch for compatibility with updated smapi-2.3.-current

 MK> By the way I have just committed FreeBSD ports for the following

Very good! (I have too low time for this)

 MK> Husky Fidosoft Project modules (I have taken latest -stable release
 MK> from sourceforge):

 MK> - bsopack-0.2.2-1
 ...
 MK> - sqpack-1.2.3-1

Please use *.2-release or later version.


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

1. echomail conferences fidosoft.husky (international) and (russian, cp866) ru.husky
2. husky project page on sf.net, "news" section

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

See huskybse/develop-doc for details.
Short description for CVS tags:
module-N_M_K-branch
where
    module - module name, e.g. fidoconfig, smapi, hpt, ...
    N      - Major version number
    M      - Minor version number
    K      - Patch level number
    branch - branch or release name: "current",
"stable" or "release"

This tag pointed to version named "module N.M.K-branch"

We (deveopers) plan make next stable branch with version numbers 1.4 for
all programs modules (hpt, htick etc but not libraries smapi &
fidoconfig) for make easy compose/build right distributives.



Stas

--- GoldED+/W32 1.1.4.7