[csw-maintainers] ARCH=all packages

[Ben Walton]

Excerpts from Philip Brown's message of Tue Nov 11 11:24:49 -0500 2008:
> only IO::Socket comes close.

Using IO::Socket to approximate wget would be painful.
 
> > 3. Include ascii-armored(/clear-signed?) versions of the applicable wget
> > binaries in the share/doc/pkgutil/bootstrap part of the packages' file
> > tree?
> 
> It's not the issue of "binary" so much as it is "arch specific".
> ascii "arch specific" data is not allowed in "ARCH=all" either.

Taking this stance would mean that shipping asm code examples for
different architectures in a doc/$assembler/examples would violate the
ARCH=all requirements too, no?

> As a side note:
> At the top level of every mirror is  "wget.sparc" and "wget.i386".
> it is fairly easy to either use perl-ftp, or /bin/ftp, to grab them
> automatically, if needed.

Yes, that would work too...automating /bin/ftp is a pita though.  And I
don't think it supports PASSIVE ftp, which may be an issue at some
sites.  HTTP is an easier target protocol from this vantage, although
lack of a nice tool by default is why we're having this discussion in
the first place! :)

I don't really care one way or another how this is eventually handled.
Ease of use for the end users should be the key requirement, so any
solution that allows them to forgo an extra manual download works for
me.

Thanks
-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20081111/ac3e7e9e/attachment-0001.asc>