Discussion:
[ast-developers] We need an alpha release, not a beta one (Re: AST rm -d compatible to POSIX rm -d?)
Irek Szczesniak
2013-12-03 18:21:54 UTC
Permalink
this will be fixed in the next release
dgk are getting together (face-2-face) to release a beta this week
We need another *alpha* release, not a beta one. There are quite a few
issues open, which all could be solved quickly if we pull together and
you accept the patches:
1. O_XATTR support is still not complete. AFAIK getconf(1) still
misses the *ATTR* attributes and needs the -f option to access
fpathconf(). chmod(1) in libcmd still misses the -@ option
2. sparse file support, i.e. hole/data support in cp(1) and mv(1), and
the lssparsemap(1) builtin should be there. I'd like to hear Roland's
opinion about this
3. ls(1) in libcmd was promised a while ago and IMHO this would be a
good thing to do

Since this would be an *alpha* it doesn't have to be perfect for us
(e.g. me), just release one. Thanks

Irek
Lionel Cons
2013-12-04 11:39:37 UTC
Permalink
Post by Irek Szczesniak
this will be fixed in the next release
dgk are getting together (face-2-face) to release a beta this week
We need another *alpha* release, not a beta one. There are quite a few
issues open, which all could be solved quickly if we pull together and
1. O_XATTR support is still not complete. AFAIK getconf(1) still
misses the *ATTR* attributes and needs the -f option to access
2. sparse file support, i.e. hole/data support in cp(1) and mv(1), and
the lssparsemap(1) builtin should be there. I'd like to hear Roland's
opinion about this
3. ls(1) in libcmd was promised a while ago and IMHO this would be a
good thing to do
Since this would be an *alpha* it doesn't have to be perfect for us
(e.g. me), just release one. Thanks
Does the transition from alpha to beta include a code or feature
freeze? Glenn, from CERN's side it would be interesting to have
lssparsemap(1) and SEEK_HOLE support integrated into cp(1) and mv(1)

Lionel

Loading...