Removed mcserver and mcfs support.
Reasons:
(1) no longer builds
(2) no one is willing to support it
(3) possibly contains unfixed security holes
(4) makes no sense in view of the availability of FISH
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
Build fails with the following message:
Installed (but unpackaged) file(s) found:
/usr/bin/mcdiff
To fix this issue %{_bindir}/mcdiff has to be added to the list of the
packaged files.
Signed-off-by: Yury V. Zaytsev <yury@shurup.com>
Added support of autodetect codepages via 'enca' program.
New parameter in user configuration file (~/.mc/ini):
[Misc]
autodetect_codeset=(one of `enca --list languages | cut -d : -f1`)
Signed-off-by: Slava Zanko <slavazanko@gmail.com>
Little code cleanup.
Signed-off-by: Ilia Maslakov <il.smind@gmail.com>
Type accuracy. Added missing includes.
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
We have a problem with the current mc-x.y.z-preW versioning scheme for
both Redhat and Debian. The problem is that
(1) mc-1:4.7.0-1.fc12.x86_64
(2) mc-1:4.7.0.pre4.231.g8cfffc5-1.fc12.x86_64
(1) is considered to be older than (2)
Signed-off-by: Slava Zanko <slavazanko@gmail.com>
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
* Bump epoch, because otherwise users wouldn't be able to upgrade
properly from older RPMs. The versioning scheme has to be revisited.
* Add changelog entry.
* Small corrections to the changelog.
Description:
If before
make dist*
./configure
was invoked without parameters next build from resulted tarball with
./configure --enable-charset
stop on error "mc.charset not found".
"./configure --enable-charset" hack before make dist* resolve this trouble.
Fix issue: In contrib/Makefile.am EXTRA_DIST variable was contain filenames relative to --enable-charset option.
Now mc.charsets file alvays present in EXTRA_DIST variable.
Signed-off-by: Slava Zanko <slavazanko@gmail.com>
Description by Sergei Trofimovich:
GNU ChangeLog? files are result of CVS stupidpity about changeset tracking.
Currently constantly updated ChangeLogs? diverge in different branches and cause collisions(!)
when 'git merge' (almost ANY SINGLE MERGE!).
Major changes can be described in NEWS file, minor changes can be autogenerated via 'git log'/'git shortlog'
and friends (if needed at all).
Adrian Bunk