From: teunis <teunis@mauve.computersupportcentre.com>
To: Jeffrey A Law <law@cygnus.com>
Cc: Robert Lipe <robertl@dgii.com>,
Joern Rennecke <amylaar@cygnus.co.uk>,
egcs@cygnus.com, Bill Walker <bw@student.ecok.edu>
Subject: Re: cpio vs. tar. was: OSR5 install of 971031
Date: Tue, 04 Nov 1997 17:31:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.971104180258.30920A-100000@sigil.computersupportcentre.com> (raw)
In-Reply-To: <11733.878663141@hurl.cygnus.com>
> > Even though X/open has marked it "to be withdrawn" and SUSv2 tags
> > it as "legacy" suggesting that "Applications should migrate to the
> > pax utility.", would any OS vendor not ship cpio?
> Lots used to not ship cpio, that's changed over time.
>
> > If we were to do anything more ambitious autoconf-ish, would it be
> > any wiser to test for pax and use it instead of either tar or cpio?
> > Then we'd have three different install-headers-* targets, and I doubt
> > that would be a lot of fun, either.
> I'd prefer to just stick with tar/cpio between those two we should
> have every significant unix covered.
>
> I wouldn't object to removing the "B" from the tar options and then
> removing cpio support -- I'm not aware of a system that doesn't ship
> tar (then again, maybe you are :-)
WindowsNT? *ducking*
G'day, eh? ;]
- Teunis
[so when's the next win32-capable image going to appear? :]
(don't answer - I'll watch for announcements)
next prev parent reply other threads:[~1997-11-04 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-03 6:23 Bill Walker
1997-11-03 8:43 ` Jeffrey A Law
1997-11-03 9:43 ` Robert Lipe
1997-11-03 16:02 ` Jeffrey A Law
1997-11-03 16:27 ` Joern Rennecke
1997-11-04 6:55 ` Jeffrey A Law
1997-11-04 7:38 ` cpio vs. tar. was: " Robert Lipe
1997-11-04 11:52 ` Jeffrey A Law
1997-11-04 17:31 ` teunis [this message]
1997-11-04 17:31 ` Jeffrey A Law
1997-11-04 16:09 ` J. Kean Johnston
1997-11-04 17:02 ` Gavin Koch
1997-11-03 9:43 ` Robert Lipe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.3.96.971104180258.30920A-100000@sigil.computersupportcentre.com \
--to=teunis@mauve.computersupportcentre.com \
--cc=amylaar@cygnus.co.uk \
--cc=bw@student.ecok.edu \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=robertl@dgii.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).