From yury at shurup.com Sun Aug 1 19:18:32 2021 From: yury at shurup.com (Yury V. Zaytsev) Date: Sun, 1 Aug 2021 21:18:32 +0200 (CEST) Subject: Help testing release candidate / mc-4.8.27-rc1 Message-ID: <11c7889c-517-e1d1-d421-71ab24aff492@shurup.com> Hi there, TLDR; I would appreciate if you could please test the following tarball on your systems and report any blocker regressions as compared to the previous 4.8.26 release: https://www.midnight-commander.org/nopaste/tarball/mc-4.8.27-pre1.tar.xz $ sha256sum mc-4.8.27-pre1.tar.xz d922e4175a20779549c4a9746bbe169d4acd2a83b2e14d1d6dfd2cbec32eb12b mc-4.8.27-pre1.tar.xz I've built this tarball out of the latest master with translations from Transifex pulled in on a fresh Fedora 33 VM, which I'm also going to use to build the final release in about a week from now if nothing serious comes up. Many thanks! -- Sincerely yours, Yury V. Zaytsev From yury at shurup.com Mon Aug 2 13:46:28 2021 From: yury at shurup.com (Yury V. Zaytsev) Date: Mon, 2 Aug 2021 15:46:28 +0200 (CEST) Subject: Help testing release candidate / mc-4.8.27-rc1 In-Reply-To: <5df22f57-86c3-48fd-7269-93e821f4e875@reagle.org> References: <11c7889c-517-e1d1-d421-71ab24aff492@shurup.com> <5df22f57-86c3-48fd-7269-93e821f4e875@reagle.org> Message-ID: On Mon, 2 Aug 2021, Joseph Reagle wrote: > I tried but: > > ``` > ... > checking build system type... Invalid configuration > `arm64-apple-darwin20.6.0': machine `arm64-apple' not recognized > configure: error: /bin/sh config/config.sub arm64-apple-darwin20.6.0 failed > ``` Hi Joseph, Oh noes, you seem to be running Apple Silicon and the autotools in Fedora Rawhide do not support it yet. Could you please try specifying the triplets by hand? If this works, then this would be the workaround until newer autotools propagate to major Linux distributions - I would be very scared of bootstrapping the official tarballs on macOS with custom Apple-patched autotools... $ CC="/usr/bin/cc" \ CFLAGS="-target arm64-apple-macos11" \ ./configure \ --host=aarch64-apple-darwin \ --target=aarch64-apple-darwin \ --build=aarch64-apple-darwin Thanks! -- Sincerely yours, Yury V. Zaytsev From yury at shurup.com Tue Aug 3 10:21:55 2021 From: yury at shurup.com (Yury V. Zaytsev) Date: Tue, 3 Aug 2021 12:21:55 +0200 (CEST) Subject: Help testing release candidate / mc-4.8.27-rc1 In-Reply-To: References: <11c7889c-517-e1d1-d421-71ab24aff492@shurup.com> <5df22f57-86c3-48fd-7269-93e821f4e875@reagle.org> Message-ID: On Mon, 2 Aug 2021, Joseph Reagle wrote: > I ran the command you suggested and the make, make install, creates a > binary in /usr/local/bin (though using homebrew arm64 commands in > /opt/homebrew) and it seems to work fine. Thanks for the confirmation! Then specifying triplets manually on Apple Silicon will be the workaround I will put in the release notes, until we get proper autotools support (hopefully) with the next release. If you are unhappy with /usr/local, you can always specify custom prefix with --prefix=$HOME/opt/mc or so. > (It doesn't include panel scrollbars from #4256?). Unfortunately, the author disappeared as suddenly as he appeared and the patch was left unfinished - thus it will not make it in this release. > BTW: During make, I get tons of warnings: > > warning: unknown warning option '-Wformat-signedness' [-Wunknown-warning-option] > warning: unknown warning option '-Wmaybe-uninitialized'; did you mean '-Wuninitialized'? [-Wunknown-warning-option] > warning: unknown warning option '-Wmissing-parameter-type' [-Wunknown-warning-option] > warning: unknown warning option '-Wunused-but-set-variable'; did you mean '-Wunused-const-variable'? I've put our chief warning officer on CC, hopefully he can say something about that - apparently our compiler flag detection is not working correctly and warning flags are supplied even though they are not supported by the compiler... Could you please post the complete build log as a compressed attachment? -- Sincerely yours, Yury V. Zaytsev From ales.janda at kyblsoft.cz Tue Aug 3 10:33:08 2021 From: ales.janda at kyblsoft.cz (=?UTF-8?Q?Ale=C5=A1_Janda?=) Date: Tue, 3 Aug 2021 12:33:08 +0200 Subject: Help testing release candidate / mc-4.8.27-rc1 In-Reply-To: References: <11c7889c-517-e1d1-d421-71ab24aff492@shurup.com> <5df22f57-86c3-48fd-7269-93e821f4e875@reagle.org> Message-ID: ?t 3. 8. 2021 v 12:22 odes?latel Yury V. Zaytsev napsal: > On Mon, 2 Aug 2021, Joseph Reagle wrote: > > > (It doesn't include panel scrollbars from #4256?). > > Unfortunately, the author disappeared as suddenly as he appeared and the > patch was left unfinished - thus it will not make it in this release. > I'm the author of that unfinished scrollbars patch. Sorry about the delays but the proper implementation with the widget group was not so easy as I expected. It just takes more time, I'm still on that. On top of that, it is a vacations season. So it should be in a month or so but not in this release. But I like that someone misses my patch :-) Ale? Janda -------------- next part -------------- An HTML attachment was scrubbed... URL: From yury at shurup.com Tue Aug 3 11:53:03 2021 From: yury at shurup.com (Yury V. Zaytsev) Date: Tue, 3 Aug 2021 13:53:03 +0200 (CEST) Subject: Help testing release candidate / mc-4.8.27-rc1 In-Reply-To: <4a1449a6-5dac-8f11-b40b-5bf24f276ce6@gmx.li> References: <11c7889c-517-e1d1-d421-71ab24aff492@shurup.com> <5df22f57-86c3-48fd-7269-93e821f4e875@reagle.org> <4a1449a6-5dac-8f11-b40b-5bf24f276ce6@gmx.li> Message-ID: <10414517-6a6-4dd9-29f9-257898688b4@shurup.com> On Tue, 3 Aug 2021, Andreas wrote: > This can happen if configure and build step run with different compiler. > > At configure step (exactly at mc-cflags.m4) compiler flags are tested > against compiler support, if supported it will added to build/make > config. Thanks for the tip! Maybe setting the compiler in my command is actually not necessary and only causes those warnings? Joseph, could you please try a clean build without setting "CC"? Thanks! -- Sincerely yours, Yury V. Zaytsev From dhmartina at yahoo.es Tue Aug 3 18:31:43 2021 From: dhmartina at yahoo.es (=?UTF-8?Q?David_Mart=c3=adn?=) Date: Tue, 3 Aug 2021 20:31:43 +0200 Subject: Help testing release candidate / mc-4.8.27-rc1 In-Reply-To: <11c7889c-517-e1d1-d421-71ab24aff492@shurup.com> References: <11c7889c-517-e1d1-d421-71ab24aff492@shurup.com> Message-ID: Compiled and run fine for Ubuntu 20.04.2 LTS. Just a couple of minor warnings: ??? ... ??? make[5]: Leaving directory '/home/dmartin/git/mc-4.8.27-pre1/src/vfs/smbfs/helpers' ??? make[5]: Entering directory '/home/dmartin/git/mc-4.8.27-pre1/src/vfs/smbfs' ??? ? CC?????? smbfs.lo ??? In file included from smbfs.c:59: **? helpers/include/config.h:458: warning: "PACKAGE_URL" redefined ??? ? 458 | #define PACKAGE_URL "" ??? ????? | ??? In file included from smbfs.c:37: **? ../../../config.h:469: note: this is the location of the previous definition ??? ? 469 | #define PACKAGE_URL "https://www.midnight-commander.org/" ??? ????? | ??? ? CCLD???? libvfs-smbfs.la **? ar: `u' modifier ignored since `D' is the default (see `U') ??? make[5]: Leaving directory '/home/dmartin/git/mc-4.8.27-pre1/src/vfs/smbfs' ??? ... Updated a bunch of Spanish translations for new SFTP/SSH faulty key warnings and uploaded them to Transifex. Please, consider merging them prior to final release, thanks!. Regards, David El 1/8/21 a las 21:18, Yury V. Zaytsev escribi?: > Hi there, > > TLDR; I would appreciate if you could please test the following > tarball on your systems and report any blocker regressions as compared > to the previous 4.8.26 release: > > https://www.midnight-commander.org/nopaste/tarball/mc-4.8.27-pre1.tar.xz > > $ sha256sum mc-4.8.27-pre1.tar.xz > d922e4175a20779549c4a9746bbe169d4acd2a83b2e14d1d6dfd2cbec32eb12b > mc-4.8.27-pre1.tar.xz > > I've built this tarball out of the latest master with translations > from Transifex pulled in on a fresh Fedora 33 VM, which I'm also going > to use to build the final release in about a week from now if nothing > serious comes up. > > Many thanks! > From yury at shurup.com Sun Aug 15 09:30:51 2021 From: yury at shurup.com (Yury V. Zaytsev) Date: Sun, 15 Aug 2021 11:30:51 +0200 Subject: Fwd: Try to wrap Midnight Commander in Rust References: Message-ID: <43D0A45E-6CAA-4083-8E87-322D5B304E73@shurup.com> Hi Vitold, Please don?t contact us using our private addresses, we don?t have the capacity to provide personal support for mc. I have forwarded your message to the development mailing list, maybe Andreas could have a look at this before next release? Sent from my iPad Begin forwarded message: > From: Vitold S > Date: 15. August 2021 at 06:10:30 CEST > To: yury at shurup.com > Subject: Try to wrap Midnight Commander in Rust > > ? > Hello, > > I am was try to make Rust wrapper for Midnight Commander in https://github.com/vit1251/mc-rs > > Since I start I receive a lot of warning message: > > warning: lib/event/manage.c: In function ?mc_event_group_destroy_value?: > warning: lib/event/manage.c:52:37: warning: cast between incompatible function types from ?void (*)(void *)? to ?void (*)(void *, void *)? [-Wcast-function-type] > warning: 52 | g_ptr_array_foreach (callbacks, (GFunc) g_free, NULL); > warning: | ^ > warning: lib/event/manage.c: In function ?mc_event_get_event_group_by_name?: > warning: lib/event/manage.c:169:30: warning: cast between incompatible function types from ?gint (*)(const gchar *, const gchar *)? {aka ?int (*)(const char *, const char *)?} to ?gint (*)(const void *, const void *, void *)? {aka ?int (*)(const void *, const void *, void *)?} [-Wcast-function-type] > warning: 169 | g_tree_new_full ((GCompareDataFunc) g_ascii_strcasecmp, > warning: | ^ > warning: lib/event/event.c: In function ?mc_event_init?: > warning: lib/event/event.c:62:26: warning: cast between incompatible function types from ?gint (*)(const gchar *, const gchar *)? {aka ?int (*)(const char *, const char *)?} to ?gint (*)(const void *, const void *, void *)? {aka ?int (*)(const void *, const void *, void *)?} [-Wcast-function-type] > warning: 62 | g_tree_new_full ((GCompareDataFunc) g_ascii_strcasecmp, > warning: | ^ > warning: lib/filehighlight/common.c: In function ?mc_fhl_array_free?: > warning: lib/filehighlight/common.c:61:44: warning: cast between incompatible function types from ?void (*)(void *)? to ?void (*)(void *, void *)? [-Wcast-function-type] > warning: 61 | g_ptr_array_foreach (fhl->filters, (GFunc) mc_fhl_filter_free, NULL); > warning: | ^ > warning: lib/search/search.c: In function ?mc_search__conditions_free?: > warning: lib/search/search.c:121:33: warning: cast between incompatible function types from ?void (*)(mc_search_cond_t *)? {aka ?void (*)(struct mc_search_cond_struct *)?} to ?void (*)(void *, void *)? [-Wcast-function-type] > warning: 121 | g_ptr_array_foreach (array, (GFunc) mc_search__cond_struct_free, NULL); > warning: | ^ > warning: lib/strutil/replace.c: In function ?str_replace_all?: > warning: lib/strutil/replace.c:112:39: warning: cast between incompatible function types from ?void (*)(void *)? to ?void (*)(void *, void *)? [-Wcast-function-type] > warning: 112 | g_ptr_array_foreach (str_splints, (GFunc) g_free, NULL); > warning: | ^ > warning: lib/widget/group.c: In function ?group_default_callback?: > warning: lib/widget/group.c:580:37: warning: cast between incompatible function types from ?void (*)(Widget *)? to ?void (*)(void *, void *)? [-Wcast-function-type] > warning: 580 | g_list_foreach (g->widgets, (GFunc) widget_destroy, NULL); > warning: | ^ > warning: src/filemanager/boxes.c: In function ?appearance_box?: > warning: src/filemanager/boxes.c:665:38: warning: cast between incompatible function types from ?void (*)(void *)? to ?void (*)(void *, void *)? [-Wcast-function-type] > warning: 665 | g_ptr_array_foreach (skin_names, (GFunc) g_free, NULL); > warning: | ^ > warning: src/filemanager/treestore.c: In function ?tree_store_notify_remove?: > warning: src/filemanager/treestore.c:483:34: warning: cast between incompatible function types from ?void (*)(void *)? to ?void (*)(struct tree_entry *, void *)? [-Wcast-function-type] > warning: 483 | tree_store_remove_fn r = (tree_store_remove_fn) p->hook_fn; > warning: | ^ > warning: src/filemanager/treestore.c: In function ?tree_store_add_entry_remove_hook?: > warning: src/filemanager/treestore.c:665:36: warning: cast between incompatible function types from ?tree_store_remove_fn? {aka ?void (*)(struct tree_entry *, void *)?} to ?void (*)(void *)? [-Wcast-function-type] > warning: 665 | add_hook (&remove_entry_hooks, (void (*)(void *)) callback, data); > warning: | ^ > warning: src/filemanager/treestore.c: In function ?tree_store_remove_entry_remove_hook?: > warning: src/filemanager/treestore.c:673:39: warning: cast between incompatible function types from ?tree_store_remove_fn? {aka ?void (*)(struct tree_entry *, void *)?} to ?void (*)(void *)? [-Wcast-function-type] > warning: 673 | delete_hook (&remove_entry_hooks, (void (*)(void *)) callback); > warning: | ^ > warning: src/viewer/growbuf.c: In function ?mcview_growbuf_free?: > warning: src/viewer/growbuf.c:99:50: warning: cast between incompatible function types from ?void (*)(void *)? to ?void (*)(void *, void *)? [-Wcast-function-type] > warning: 99 | g_ptr_array_foreach (view->growbuf_blockptr, (GFunc) g_free, NULL); > warning: | ^ > warning: src/editor/choosesyntax.c: In function ?edit_syntax_dialog?: > warning: src/editor/choosesyntax.c:144:33: warning: cast between incompatible function types from ?void (*)(void *)? to ?void (*)(void *, void *)? [-Wcast-function-type] > warning: 144 | g_ptr_array_foreach (names, (GFunc) g_free, NULL); > warning: | ^ > warning: src/editor/editbuffer.c: In function ?edit_buffer_clean?: > warning: src/editor/editbuffer.c:168:39: warning: cast between incompatible function types from ?void (*)(void *)? to ?void (*)(void *, void *)? [-Wcast-function-type] > warning: 168 | g_ptr_array_foreach (buf->b1, (GFunc) g_free, NULL); > warning: | ^ > warning: src/editor/editbuffer.c:174:39: warning: cast between incompatible function types from ?void (*)(void *)? to ?void (*)(void *, void *)? [-Wcast-function-type] > warning: 174 | g_ptr_array_foreach (buf->b2, (GFunc) g_free, NULL); > warning: | ^ > warning: src/editor/syntax.c: In function ?context_rule_free?: > warning: src/editor/syntax.c:162:42: warning: cast between incompatible function types from ?void (*)(void *)? to ?void (*)(void *, void *)? [-Wcast-function-type] > warning: 162 | g_ptr_array_foreach (r->keyword, (GFunc) syntax_keyword_free, NULL); > warning: | ^ > warning: src/editor/syntax.c: In function ?edit_free_syntax_rules?: > warning: src/editor/syntax.c:1445:39: warning: cast between incompatible function types from ?void (*)(void *)? to ?void (*)(void *, void *)? [-Wcast-function-type] > warning: 1445 | g_ptr_array_foreach (edit->rules, (GFunc) context_rule_free, NULL); > warning: | > > Could you please fix these warning messages in next releases? > > Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dnh at opensuse.org Sun Aug 15 11:40:33 2021 From: dnh at opensuse.org (David Haller) Date: Sun, 15 Aug 2021 13:40:33 +0200 Subject: Fwd: Try to wrap Midnight Commander in Rust In-Reply-To: <43D0A45E-6CAA-4083-8E87-322D5B304E73@shurup.com> References: <43D0A45E-6CAA-4083-8E87-322D5B304E73@shurup.com> Message-ID: <20210815114033.j5t4d7oaw4tikyda@grusum.endjinn.de> Hello, On Sun, 15 Aug 2021, Yury V. Zaytsev wrote: >Begin forwarded message: >> From: Vitold S [..] >> warning: lib/event/manage.c: In function 'mc_event_group_destroy_value': >> warning: lib/event/manage.c:52:37: warning: cast between incompatible function types from 'void (*)(void *)' to 'void (*)(void *, void *)' [-Wcast-function-type] >> warning: 52 | g_ptr_array_foreach (callbacks, (GFunc) g_free, NULL); >> warning: | ^ Just taking the first warning as an example: this has nothing to do with mc, this is a glib-2 upstream issue. In e.g. glib-2.68.3 we have these decls: glib/garray.h: void g_ptr_array_foreach(GPtrArray *array, GFunc func, gpointer user_data); The 'GFunc func' is the function pointer being cast. Also: glib/gtypes.h: typedef void (*GFunc) (gpointer data, gpointer user_data); and glib/gmem.h: void g_free (gpointer mem); The only way around these conflicting types (that I see) is an (inlined) wrapper function around g_free. Actually, I'd just use '-Wno-cast-function-type' or omit the '-Wextra'. HTH, -dnh -- Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. -- Douglas N. Adams, Last Chance To See From yury at shurup.com Sun Aug 15 14:36:26 2021 From: yury at shurup.com (Yury V. Zaytsev) Date: Sun, 15 Aug 2021 16:36:26 +0200 (CEST) Subject: Midnight Commander 4.8.27 released Message-ID: <9ffc9d5c-18df-8cdb-ad82-707f29bf3c79@shurup.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, I'm glad to announce the immediate availability of mc-4.8.27, a maintenance and security release, just in time before leaving all of you for a long overdue summer vacation! This release addresses an important security issue (CVE-2021-36370) in the SFTP VFS. Unfortunately, as the VFS was first introduced, the fingerprints of remote hosts were computed, but not verified, and the issue reported only now by Manfred KAISER from AUT-milCERT during an audit of open source software. We would like to thank the team at AUT-milCERT for finding the issue and responsibly disclosing it! Other than that there is a large slew of assorted bugfixes to various subsystems. For the detailed list of changes since the last release, please refer to the release notes. Everybody is recommended to upgrade to immediately benefit from these improvements! Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.27 Unfortunately, the autotools support for Apple M1 has not propagated widely enough, so if you need to build mc on such a system, you will have to specify the triplets manually - hopefully this will be no longer necessary by the time of the next release: CFLAGS="-target arm64-apple-macos11" \ ./configure \ --host=aarch64-apple-darwin \ --target=aarch64-apple-darwin \ --build=aarch64-apple-darwin As usual, thanks to Andrew Borodin, who was the main driving force behind this release, as well as all of our contributors, including translators. Have fun! - -- Sincerely yours, Yury V. Zaytsev -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJhGSZwAAoJEPci7nm8u+Dv7tUP/3UZEBUrTcCoY5I6p+9jTZni 2EXvl3qWuKK+2F0WOpztNAct0b6kyMOqtfH2VsRB6Set/8vhY9bx6b48cnZhkUR0 WTlmGq/eK1KTYfac7oYwp7RfknJ4jS99MdJXKUu9tukTD/QP+iBURhC+xTnh/yrJ fzWn6UEsvHvDoHDFyZi0C8UYIbCd+XNyaxQNtJANf8SAwAtzTEcvhs63DX6DAJm2 uARL1EiKT2D0HCELSRhEAH+XwYEkd+4N8nWBaB1mo3TditY7bbFW/c+TV+Z78Cxq p2RsoAhEDSPAyPBYpzXvYwQ2OgX56ug+wKMqjlYWtTYSC+Z6jqtZhYb2Mg9beY8e B6gE5w9h//UA7zPqt01+LN4ErdHUyUejpk6eBYX7z/RABaURGZ41GaCEnxhcULnZ lwOzU19puEFRIG5L1gXAr5KiTTh5/ALdn7OyxrXIVd4HRosFXSbZVwCAcWPdL2uj 17Na5volVN1VSD225/RJ8BnP0PWNxPlnpfSUEHJnaz0FWrwgE3oHHvMmkPQ6JbOP ap0uZZyebtaUBHLL3gvriu/SKTWvT/VMGgbDi660mN5pKYgtbYDzqjy4SR38hQmX 27xD6pKFIFM7kQReeqc6sXq+SckuMYs2rpmDYVlj/eIacqAWPArTgDuWZ/sqbS+e /6JHh/vU7I1JxZXmfl5o =qJEm -----END PGP SIGNATURE----- From info at metux.net Mon Aug 16 15:34:33 2021 From: info at metux.net (Enrico Weigelt, metux IT consult) Date: Mon, 16 Aug 2021 17:34:33 +0200 Subject: Fwd: Try to wrap Midnight Commander in Rust In-Reply-To: <43D0A45E-6CAA-4083-8E87-322D5B304E73@shurup.com> References: <43D0A45E-6CAA-4083-8E87-322D5B304E73@shurup.com> Message-ID: On 15.08.21 11:30, Yury V. Zaytsev wrote: Hello friends, >> I am was try to make Rust wrapper for Midnight Commander in >> https://github.com/vit1251/mc-rs could anyone please enlighten me, what's that all about ? Why replacing the well tested current automake build system by an rust program ? Just for the sake of calling it via cargo commend ? And if so, why not just calling the usual build system ? --mtx -- --- Hinweis: unverschl?sselte E-Mails k?nnen leicht abgeh?rt und manipuliert werden ! F?r eine vertrauliche Kommunikation senden Sie bitte ihren GPG/PGP-Schl?ssel zu. --- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering info at metux.net -- +49-151-27565287 From info at metux.net Tue Aug 17 14:56:00 2021 From: info at metux.net (Enrico Weigelt, metux IT consult) Date: Tue, 17 Aug 2021 16:56:00 +0200 Subject: Fwd: Try to wrap Midnight Commander in Rust In-Reply-To: References: <43D0A45E-6CAA-4083-8E87-322D5B304E73@shurup.com> Message-ID: On 16.08.21 18:40, Vitold S wrote: Hi, > With regard to my research, there is no required legacy building system > anymore. from Distro perspective, cargo *is* a legacy build system, which is focused to rust only and pretty much opposes the whole concept of distros as such. Getting rust stuff (beginning with the toolchain itself) up and running in a Distro context is a really painful and complicated - and rust itself is a moving target. > cargo provides a dependency graph: We already have that with the existing build tools. And much more than you now have with your explicitly open-coded build program, which is only capable of handling a very small subset of what the current build system (autotools) supports. If you wanted to catch up, you'd essentially have to rewrite the whole 'configure' script (which is auto-generated by autoconf) plus all makefiles in rust. Once you've done that you've achieved nothing more than just adding a massive and highly problematic dependency: the rust toolchain. A software entirely written in C now needs a very exotic programming language just for being compiled: rust. > ncurses, glib and any other provided by cargo as Rust crate (in theory, > but in practice you may see a lot of issues in crates but it is Rust ecosystem problem). Yes, you're right: the rust ecosystem *is* *the* problem. The core Rust folks seem to believe that everything not written in rust is just bad code that needs to go away and distros with their package management are the worst of all evil. Not surprising that it took many years for rust being added to some distros and upgrades take so extremely long to get into distros. > > Just for the sake of calling it via cargo commend ? > > Yep. Actually for delegate maintenance to the module owner (you may see > that GTK is owned by GTK Team). What kind of maintenance exactly ? Mc takes the libs from the distros. It uses the standard pkg-config mechamism for lookup and flags retrieval. This works smoothly for decades. mc is using this since 20 years (minus three weeks, to be precise). > As I see most crates use cmake, automake or make under hood and failed > by some reasons on some platforms. > It is not a well porting procedure and as result provides broken crates. And nobody consideres the whole idea as such might be wrong ? > > And if so, why not just calling the usual build system ? > > Rust provides a way to replace C code by chunking. You may see that I > replace tty/tty-ncurses/tty-slang by > ncurses crate (5.7 on my system on macOs) and try pancurses crate in > referred files tty_ncurses.rs and > tty_pancyurses.rs So you wanna replace the already existing ncurses library (which is most likely already installed on any machine where mc is installed, or will be installed fully automatically by package manager if needed) by some quite untested piece of rust code ? What for ? And also entirely drop slang support ? I recall (probably around 2k6..2k8) we had long and heated discussions on whether we drop or keep it. We finally decided that there're good reasons to keep it, eg. for low end machines that prefer the smaller slang instead of ncurses. > Unfortunately, my platform does not contain builttin ncursesw (macOs) or > GNU autootols and I does not have ability to make Rust crates ncursesw. brew install ncurses brew install automake > Using build.rs provide hybrid building with part of C > and Rust code both at the same time without any pain and additional > support requirements. Why building rust code in mc at all ? Do you wanna rewrite mc in rust ? Then you'd better start completely afresh. (and give it a different name). --mtx -- --- Hinweis: unverschl?sselte E-Mails k?nnen leicht abgeh?rt und manipuliert werden ! F?r eine vertrauliche Kommunikation senden Sie bitte ihren GPG/PGP-Schl?ssel zu. --- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering info at metux.net -- +49-151-27565287 From yury at shurup.com Tue Aug 17 15:19:42 2021 From: yury at shurup.com (Yury V. Zaytsev) Date: Tue, 17 Aug 2021 17:19:42 +0200 (CEST) Subject: Fwd: Try to wrap Midnight Commander in Rust In-Reply-To: References: <43D0A45E-6CAA-4083-8E87-322D5B304E73@shurup.com> Message-ID: On Tue, 17 Aug 2021, Enrico Weigelt, metux IT consult wrote: > Why building rust code in mc at all ? > > Do you wanna rewrite mc in rust ? Then you'd better start completely > afresh. (and give it a different name). He did give it a different (working) name - mc-rs - he's published his experiment on his own GitHub account and has invited anyone who is interested to contribute. All fine by me... Since the original post contained questions about compiler warnings pertaining to the mc source code, I have forwarded it to this list, where it was quickly and helpfully answered. If you have important opinions to share on Rust, please find a different forum for this though. But before you do, I'd urge you to rethink whether this is necessary in the first place... Vitold is like anyone else entitled to use his time however he wants, and if he set out to rewrite mc in Rust, it's up to him to decide whether he should do it incrementally or by starting from scratch. -- Sincerely yours, Yury V. Zaytsev From subscript at free.fr Wed Aug 25 15:50:01 2021 From: subscript at free.fr (wwp) Date: Wed, 25 Aug 2021 17:50:01 +0200 Subject: Midnight Commander 4.8.27 released In-Reply-To: <9ffc9d5c-18df-8cdb-ad82-707f29bf3c79@shurup.com> References: <9ffc9d5c-18df-8cdb-ad82-707f29bf3c79@shurup.com> Message-ID: <20210825175001.0876313f@solud> Hello Yury, On Sun, 15 Aug 2021 16:36:26 +0200 (CEST) "Yury V. Zaytsev" wrote: > Hi there, > > I'm glad to announce the immediate availability of mc-4.8.27, a maintenance and security release, just in time before leaving all of you for a long overdue summer vacation! [snip] Thanks for this new release, and all the efforts underneath! Quickly built from the sources on a CentOS 7 system.. I notice that on a regular basis, mc starts w/ no subshell, most of the time with it. Nothing in output that would bring a tip, it's just that there is no subshell available from time to time. I'm tempted to say that it happens more when the system is busy (cpu), but I won't bet this is related. GNU Midnight Commander 4.8.27 Built with GLib 2.56.1 Built with S-Lang 2.2.4 with terminfo database With builtin Editor and Aspell support With subshell support as default With support for background operations With mouse support on xterm and Linux console With support for X11 events With internationalization support With multiple codepages support With ext2fs attributes support Virtual File Systems: cpiofs, tarfs, sfs, extfs, ftpfs, sftpfs, fish, smbfs Data types: char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64; Regards, -- wwp https://useplaintext.email/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: From sgniazdowski at gmail.com Sun Aug 29 07:40:30 2021 From: sgniazdowski at gmail.com (Sebastian Gniazdowski) Date: Sun, 29 Aug 2021 09:40:30 +0200 Subject: Triggering actions from outside? Message-ID: I thought that it would be nice to trigger CK_EditNew and other actions when running a macro, or a usermenu entry. It can be done via signals (USR1), attached is a patch. For running from macros inside mc/mcedit, what's sufficient is to execute: mc --ck EditNew (because the pid is exported). For outside, one has to specify the pid via: MC_PID=1234 mc --ck EditNew. It works for mc and mcedit. What do you think? PS. A little video: asciinema.org/a/432747 -- Best regards, Sebastian Gniazdowski -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Signal_CK_actions.patch Type: text/x-patch Size: 11729 bytes Desc: not available URL: