I for one, would prefer POSIX compliance. :)
> $ tar -cl foo
> Error: -l has different behaviors in different tars.
> For the GNU behavior, use --one-file-system instead.
> For the POSIX behavior, use --check-links instead.
How about turning this into a warning?
> I don't believe the change to -l will break more than a couple
> of ports. Prior to this change, ports that specified
> -l would get the POSIX behavior even though they
> may have thought they were requesting the GNU
> behavior. This change will force you to unambiguously
> specify the particular behavior you desire.
>
> In short, everyone wins on -o, everyone loses
> on -l. That seems fair. ;-)
I believe "loses" is the keyword here. I don't see how this
would benefit anyone in the long term, sticking with either
side would be better (but please choose POSIX :).
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
Well, '-l' has meant "local filesystem only" in FreeBSD since the 1.0
release (i.e. since the beginning - more than 10 years now). FreeBSD isn't
a POSIX OS - it's a BSD OS and we have many differences in our user
environment that differ from POSIX. That's partly what makes us BSD rather
than System V, Solaris, or Linux. Many of our users prefer the way that ps(1)
works in BSD, for example...as well as many other non-POSIXisms in other
utilities.
Since I personally trashed a destination filesystem because the new tar
didn't do the right thing, I *know* there will be many other unsuspecting
FreeBSD users that will have a similary distasteful experience with such
a completely different behavior of '-l'.
-DG
David G. Lawrence
President
Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500
TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175
The FreeBSD Project - http://www.freebsd.org
Pave the road of life with opportunities.
_______________________________________________
freebs...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-port...@freebsd.org"
> presence of POSIXLY_CORRECT.) I will consider
> suggestions for a corresponding environment variable
> for GNU behavior (GNULY_CORRECT?).
My suggestion: don't bother about GNULY_CORRECT. Where GNU deviates from
standards without good reason, GNU needs to be fixed.
--
Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred)
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
I do not digest ice cream well. I demand that a suitable ice cream
replacement be made available by default. Ice cream should be served
only if it receives --with-lactose.
Furthermore, which flavour and colour of ice cream are we talking here?
# Adam
What. I just woke up.
--
Adam Weinberger
ad...@magnesium.net || ad...@FreeBSD.org
ad...@vectors.cx || ad...@gnome.org
http://www.vectors.cx
A bikeshed in an ice-cream disguise! It's amazing how things transmute ;)
| # Adam
|
| What. I just woke up.
|
+----]
Have a nice day!
Fernan
--
Fernan Aguero - fernan at iib.unsam.edu.ar
Phone: +54 11 4580-7255/7 ext 310, Fax: +54 11 4752-9639
Check http://genoma.unsam.edu.ar/~fernan for more info.
_______________________________________________
freebs...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-port...@freebsd.org"
'GNU_ME_HARDER'.
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
Works here. Which means either there's something
weird going on at your end, or something weird going
on at my end.
It's possible you managed to get it in the middle
of a cvs update, I suppose. Try updating again
and rebuilding src/lib/libarchive and src/usr.bin/tar
and let me know if that changes anything.
Out of curiosity, what does "ls -l .bashrc" show?
Tim
_______________________________________________
freebs...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-port...@freebsd.org"