RFC: busybox 1.2.3?

[Bernhard Fischer]

On Wed, Dec 13, 2006 at 01:48:47AM +0100, Denis Vlasenko wrote:
>Hi people,
>
>It seems I fixed "make release" to actually work again.
>I am thinking about releasing next version so that
>people will try & break changed stuff.
>
>I think kernel's way of having bugfix releases
>with fourth number (x.y.z.N) will work for us too.
>
>Any thoughts what should be done before releasing 1.2.3?

There is one long-standing bug that would be really nice if it was
finally fixed for good:

- Specifying a path to df doesn't work. There's also a bugreport about
  this (or two):
  $ ./busybox df -k / ; echo $?
  Filesystem           1k-blocks      Used Available Use% Mounted on
  0
  $ df -k / ; echo $?
  Filesystem           1K-blocks      Used Available Use% Mounted on
  /dev/hda1             67282996  58701576   7214292  90% /
  0
  $ grep hda1 /proc/mounts 
  /dev/hda1 / ext3 rw,data=ordered,usrquota,grpquota 0 0
  /dev/hda1 /dev/.static/dev ext3 rw,data=ordered,usrquota,grpquota 0 0

Another one that looks like it will affect several cases where busybox
is used (desktop boot system):
- IIRC readlink -f /nonexisting_file does print the nonexisting file in
  current coreutils as oopposed to our impl. It's used in several sysv
  scripts in distros, i think, so we should match the current coreutils
  impl.
  $ ./busybox readlink -f /nono ; echo $?
  1
  $ readlink -f /nono ; echo $?
  /nono
  0
  $ readlink --version | head -n 1
  readlink (GNU coreutils) 5.97


Some notes concerning the release branch:
1) please don't forget to do a
svn cp ../trunk/busybox .../branches/busybox-1_3-stable
This should be done for any release.
2) Please create a tag for the actual 1.3.0 release (in the -stable
branch, perhaps). This should imo be done for any release.
3) Please do not forget to remove the -Werror from Makefile.flags for
the stable series. It may be nice to have for development, but breaking
to build for users because of it sounds like it will trigger
complaints..