Re: Getting ready for a release
Just FYI - http://mc.redhat-club.org. Another fork, and it is included in tigro repo for Fedora. They recently released version 4.6.3. On Wed, 20 Aug 2008 00:06:34 +0300 Nerijus Baliunas neri...@users.sourceforge.net wrote: Hello, are there any plans for a new release? On Tue, 04 Sep 2007 10:57:42 +0200 Pavel Tsekov ptse...@gmx.net wrote: Hello, As it has been discussed on the mailing list a new release of MC is long overdue. So... I plan to release a new version of MC by mid October. This gives us about a month (till the end of September) for final testing, bug reporting, fixing, updating translations and other related tasks - the last two are to be used by translators to update the MC translation. I hope that everyone interested will participate in this process so that we can finally release a new version. There are three full weeks by the end of September which can be used to release at most 3 pre-releases and give each a week of testing and polishing (depending on the user feedback). I am going to wait till the end of this week for your suggestions on how to use the remaining three weeks and make a plan according to them, then I'll publish the first pre-release on Monday. This reminds me that we have another problem to solve - how are we going to number the new release ? Please, share your thoughts on that too. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Getting ready for a release
Hello, are there any plans for a new release? On Tue, 04 Sep 2007 10:57:42 +0200 Pavel Tsekov [EMAIL PROTECTED] wrote: Hello, As it has been discussed on the mailing list a new release of MC is long overdue. So... I plan to release a new version of MC by mid October. This gives us about a month (till the end of September) for final testing, bug reporting, fixing, updating translations and other related tasks - the last two are to be used by translators to update the MC translation. I hope that everyone interested will participate in this process so that we can finally release a new version. There are three full weeks by the end of September which can be used to release at most 3 pre-releases and give each a week of testing and polishing (depending on the user feedback). I am going to wait till the end of this week for your suggestions on how to use the remaining three weeks and make a plan according to them, then I'll publish the first pre-release on Monday. This reminds me that we have another problem to solve - how are we going to number the new release ? Please, share your thoughts on that too. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Getting ready for a release
On Tuesday 04 September 2007 09:57, Pavel Tsekov wrote: Hello, As it has been discussed on the mailing list a new release of MC is long overdue. So... I plan to release a new version of MC by mid October. This gives us about a month (till the end of September) for final testing, bug reporting, fixing, updating translations and other related tasks - the last two are to be used by translators to update the MC translation. I hope that everyone interested will participate in this process so that we can finally release a new version. There are three full weeks by the end of September which can be used to release at most 3 pre-releases and give each a week of testing and polishing (depending on the user feedback). I am going to wait till the end of this week for your suggestions on how to use the remaining three weeks and make a plan according to them, then I'll publish the first pre-release on Monday. This reminds me that we have another problem to solve - how are we going to number the new release ? Please, share your thoughts on that too. Please include the following patches: [PATCH] 'a' and 'b' are the same file/directory message box needs Abort button. http://www.mail-archive.com/mc-devel@gnome.org/msg05524.html and Fwd: [PATCH] make old escmode key timeout configurable http://osdir.com/ml/gnome.apps.mc.devel/2004-10/msg00212.html Attached versions of these patches apply cleanly to 1.6.1. Thanks, -- vda diff -urpN mc-4.6.1.org/src/key.c mc-4.6.1/src/key.c --- mc-4.6.1.org/src/key.c 2005-06-08 14:27:19.0 +0200 +++ mc-4.6.1/src/key.c 2007-05-18 13:49:17.0 +0200 @@ -73,7 +73,7 @@ (t2.tv_usec-t1.tv_usec)/1000) /* timeout for old_esc_mode in usec */ -#define ESCMODE_TIMEOUT 100 +#define ESCMODE_TIMEOUT keyboard_key_timeout /* Linux console keyboard modifiers */ #define SHIFT_PRESSED 1 @@ -85,6 +85,7 @@ int mou_auto_repeat = 100; int double_click_speed = 250; int old_esc_mode = 0; +int keyboard_key_timeout = 100; /* settable via env */ int use_8th_bit_as_meta = 0; @@ -427,6 +428,10 @@ init_key (void) { const char *term = getenv (TERM); +char *kt = (char *)getenv(KEYBOARD_KEY_TIMEOUT_US); +if (kt != NULL) + keyboard_key_timeout = atoi(kt); + /* This has to be the first define_sequence */ /* So, we can assume that the first keys member has ESC */ define_sequences (mc_default_keys); diff -urpN mc-4.6.1.org/src/utilunix.c mc-4.6.1/src/utilunix.c --- mc-4.6.1.org/src/utilunix.c 2005-07-23 18:52:03.0 +0200 +++ mc-4.6.1/src/utilunix.c 2007-05-18 13:42:31.0 +0200 @@ -240,8 +240,9 @@ mc_tmpdir (void) struct stat st; const char *error = NULL; -/* Check if already initialized */ -if (tmpdir) +/* Check if already initialized and still exists */ +/* (some people run automatic /tmp cleaners...) */ +if (tmpdir lstat (tmpdir, st) == 0) return tmpdir; sys_tmp = getenv (TMPDIR); diff -urpN mc-4.6.1.org/src/file.c mc-4.6.1.cp/src/file.c --- mc-4.6.1.org/src/file.c 2005-05-27 16:19:18.0 +0200 +++ mc-4.6.1.cp/src/file.c 2007-05-18 16:00:23.0 +0200 @@ -458,6 +458,25 @@ enum { DEST_FULL /* Created, fully copied */ }; +static int warn_same_file(const char *fmt, const char *a, const char *b) +{ +char *msg; +/* We don't expect %d etc, just %s, so strlen(fmt) should be ok */ +int n = strlen(fmt) + strlen(a) + strlen(b) + 1; + +msg = malloc(n); +if (msg) { + snprintf(msg, n, fmt, a, b); + n = query_dialog (MSG_ERROR, msg, + D_ERROR, 2, _(Skip), _(Abort)); + free(msg); + do_refresh (); + if (n) /* 1 == Abort */ + return FILE_ABORT; +} +return FILE_SKIP; +} + int copy_file_file (FileOpContext *ctx, const char *src_path, const char *dst_path, int ask_overwrite, off_t *progress_count, @@ -512,12 +531,9 @@ copy_file_file (FileOpContext *ctx, cons if (dst_exists) { /* Destination already exists */ - if (sb.st_dev == sb2.st_dev sb.st_ino == sb2.st_ino) { - message (1, MSG_ERROR, - _( `%s' and `%s' are the same file ), src_path, dst_path); - do_refresh (); - return FILE_SKIP; - } + if (sb.st_dev == sb2.st_dev sb.st_ino == sb2.st_ino) + return warn_same_file(_( `%s' and `%s' are the same file ), +src_path, dst_path); /* Should we replace destination? */ if (ask_overwrite) { @@ -1043,22 +1059,8 @@ move_file_file (FileOpContext *ctx, cons if (mc_lstat (d, dst_stats) == 0) { if (src_stats.st_dev == dst_stats.st_dev - src_stats.st_ino == dst_stats.st_ino) { - int msize = COLS - 36; - char st[MC_MAXPATHLEN]; - char dt[MC_MAXPATHLEN]; - - if (msize 0) - msize = 40; - msize /= 2; - - strcpy (st, path_trunc (s, msize)); - strcpy (dt, path_trunc (d, msize)); - message (1, MSG_ERROR, - _( `%s' and `%s' are the same file ), st, dt); - do_refresh (); - return FILE_SKIP; - } + src_stats.st_ino == dst_stats.st_ino) +
Getting ready for a release
Hello, As it has been discussed on the mailing list a new release of MC is long overdue. So... I plan to release a new version of MC by mid October. This gives us about a month (till the end of September) for final testing, bug reporting, fixing, updating translations and other related tasks - the last two are to be used by translators to update the MC translation. I hope that everyone interested will participate in this process so that we can finally release a new version. There are three full weeks by the end of September which can be used to release at most 3 pre-releases and give each a week of testing and polishing (depending on the user feedback). I am going to wait till the end of this week for your suggestions on how to use the remaining three weeks and make a plan according to them, then I'll publish the first pre-release on Monday. This reminds me that we have another problem to solve - how are we going to number the new release ? Please, share your thoughts on that too. -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Getting ready for a release
On Tue, Sep 04, 2007 at 10:57:42AM +0200, Pavel Tsekov wrote: how are we going to number the new release ? 4.7. no exaggerated humbleness, please. -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Getting ready for a release
On Tue, Sep 04, 2007 at 10:57:42AM +0200, Pavel Tsekov wrote: how are we going to number the new release ? /me votes for 4.6.2. As far as I followed the development, there's nothing really brand new huge or conceptual change that would make calling it 4.7 reasonable, it only contains plenty of small bugfixes. Being a maintainer of a distro what I see is that by now every Linux distribution that matters has switched to using UTF-8, and mc is amongst the really very very few packages that still need to be patched to work correctly in such environments. (I think mc is the only one where lack of utf-8 support is immediately seen by the users and makes it nearly unusable in such systems). Hence distros will still have to patch mc for UTF-8, just as they did with 4.6.1. It also implies that users won't be able to simply download and compile and use this brand new mc - they'll have to wait for their distributors to update the package, which probably don't happen immediately due to the work required on their side. So IMHO UTF-8 support out of the box is a must for the version named 4.7. -- Egmont ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Getting ready for a release
On Tuesday 04 September 2007 10:18, Oswald Buddenhagen wrote: On Tue, Sep 04, 2007 at 10:57:42AM +0200, Pavel Tsekov wrote: how are we going to number the new release ? 4.7. no exaggerated humbleness, please. 4.7.0. Fixes can go to stable 4.7.x, big changes to eventual 4.8.0... -- vda ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Getting ready for a release
Original-Nachricht Datum: Tue, 4 Sep 2007 14:43:53 +0200 Von: Egmont Koblinger An: Pavel Tsekov Betreff: Re: Getting ready for a release Being a maintainer of a distro what I see is that by now every Linux distribution that matters has switched to using UTF-8, and mc is amongst the really very very few packages that still need to be patched to work correctly in such environments. (I think mc is the only one where lack of utf-8 support is immediately seen by the users and makes it nearly unusable in such systems). Lack of UTF-8 support is a big minus on the part of MC, but I think that your statement is a bit overestimated. It's more like MC is not following the latest trend, IMO. Hence distros will still have to patch mc for UTF-8, just as they did with 4.6.1. It also implies that users won't be able to simply download and compile and use this brand new mc - they'll have to wait for their distributors to update the package, which probably don't happen immediately due to the work required on their side. MC on all major distros comes with the UTF-8 patch. MC in CVS is not different than the snapshots most of the distros use to build their packages - maybe there are some who stick to the 4.6.1 release though. So IMHO UTF-8 support out of the box is a must for the version named 4.7. I haven't looked at the UTF-8 patch recently (but I will) so I cannot comment it. Do you think that UTF-8 patch 'as is' is the right way to implement UTF-8 for MC ? And what about ncurses - it is my opinion that it must not be dropped in favor of S-Lang... -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Getting ready for a release
On Tuesday 04 September 2007 09:57, Pavel Tsekov wrote: Hello, As it has been discussed on the mailing list a new release of MC is long overdue. So... I plan to release a new version of MC by mid October. This gives us about a month (till the end of September) for final testing, bug reporting, fixing, updating translations and other related tasks - the last two are to be used by translators to update the MC translation. I hope that everyone interested will participate in this process so that we can finally release a new version. I am currently watching this Google tech talk: http://kernel.org/doc/video.html April 19, 2007 Release Management in Large Free Software Projects - Martin Michlmayr (Debian) ABSTRACT: Time based releases are made according to a specific time interval, instead of making a release when a particular functionality or set of features have been implemented. This talk argues that time based release management acts as an effective coordination mechanism in large volunteer projects and shows examples from seven projects that have moved to time based releases: Debian, GCC, GNOME, Linux, OpenOffice, Plone, and X.org. Direct link to video: http://video.google.com/videoplay?docid=-5503858974016723264 Maybe it will be interesting to you too. -- vda ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Getting ready for a release
Hi! April 19, 2007 Release Management in Large Free Software Projects I cannot do much on the C programming side (I am rather into Java, shell and a few other things, but just in case you are interested in agile project management: I am a Certified Scrum Master (cf. my web site, http://scrum-master.de) and might be able to offer free services to your project, depending on my clients, ongoing commercial projects and coaching classes I am involved in. Pavel, this is not supposed to turn into a sales pitch thing, so if you are interested at all, send a private e-mail so we can discuss this off-line. Regards -- Alexander Kriegisch ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel