This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ITP] busybox 1.23.2-1


On Jun 26 13:35, Christian Franke wrote:
> Corinna Vinschen wrote:
> > On Jun 25 23:18, Christian Franke wrote:
> >> I would like to contribute the BusyBox multi-call binary.
> >>
> >> http://www.busybox.net/
> >>
> >> ...
> >>
> > Packaging looks good, but...
> >
> > AFAIU busybox-standalone is what the name suggests.  It's the version of
> > busybox with the builtin commands.  So, wouldn't that be the preferred
> > option of running busybox?
> >
> > What I'm trying to say is, I'd expect that standalone busybox is
> > installed into /usr/bin, rather than hidden under
> > /usr/libexec/busybox-standalone/  It would use the commands from
> > /usr/bin for everything not in busybox itself, which sounds like a good
> > idea to me.
> 
> One reason for the decision to symlink /usr/bin/busybox to the 
> non-standalone version was that upstream declares the standalone feature 
> still as experimental.
> 
> Both variants have its pros and cons.
> The standalone shell could run all builtins without symlinks and PATH.
> Drawback: Single builtins could not be replaced by external commands.
> 
> Hmm... it possibly would make sense to use alternatives(8) for the 
> /usr/bin/busybox symlink
> (and move man page and doc files to a separate busybox-doc package).

Sounds like a plan :)

> Note that both versions could be used to create a tiny 'portable' Cygwin 
> by copying libexec/busybox{,-standalone} to /some/where.
> Which variant is best depends on the use case.
> 
> 
> >
> > The non-standalone busybox OTOH, is something which is better off
> > encapsulated into /usr/libexec/busybox/ I think.  It comes with a set of
> > commands already available.  What's the sense except for testing
> > purposes?
> 
> On a small Cygwin installation, install busybox and set
> 
> PATH=/usr/local/bin:/usr/bin:/usr/libexec/busybox/bin
> 
> This will add tiny versions of various commands if the full package is 
> not installed.
> Some busybox commands not included in Cygwin "Base" install: > bzip2, cpio, dos2unix, free, ftpget/put, hexdump, nc, pipe_progress, pscan,
> pstree, unix2dos, telnet, top, watch, wget, which, unlzma, unzip, unxz.
> 
> IMO not too bad for a single exe which is smaller than bash.exe :-)

Indeed.

> >> The debug package for the 64-bit version is still missing. I didn't find out
> >> yet why cygport does only build the 32-bit debug package. Thanks for any
> >> help.
> > Hmm, weird.  Usually that occurs if your executables are stripped during
> > installation, or if the gcc CLI options required to build the debuginfo
> > are not propageted to the make process correctly.  But it beats me why
> > this should differe between 32 and 64 bit.
> 
> Today I retried on another machine and it works. Looks like there is 
> some interesting problem in the Cygwin 64 installation on my build 
> machine :-)
> 
> The final 64-bit version will provide a debug package.

Cool.  I entered busybox to the package list, so feel free to upload
when you're ready.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: pgpZzlBP2w0oY.pgp
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]