On Sun, 2016-05-15 at 01:57 +0200, Martin Matuska wrote: > That switch is "--insecure" and is supported in all libarchive > versions > freebsd ever used. > Oh, well that will make handling the new version easier. It doesn't change the fact that the new libarchive stuff will break long-working existing software, but at least it'll be easy to fix. -- Ian > > On 15.05.2016 01:36, Ngie Cooper (yaneurabeya) wrote: > > > On May 14, 2016, at 16:29, Martin Matuska <mm_at_FreeBSD.org> wrote: > > > > > > Ian, we are here talking about cpio, not libarchive. The flag in > > > libarchive is not active by default. > > > > > > On 14.05.2016 22:08, Ian Lepore wrote: > > > > The real damage will happen to out-of-tree users. I think this > > > > will > > > > impact our software updater for $work for example, and it has > > > > to work > > > > with both old and new versions of libarchive, and now the new > > > > version > > > > will require a flag that the old version will reject as > > > > unknown. > > > > > > > > Ick. > > Ian’s comment was valid.. cpio doesn’t recognize the new switch on > > older versions, so something like cpio `cpio --help | grep -- > > switch && echo switch` would need to be employed everywhere for > > backwards compatibility — ew. > > Thanks, > > -Ngie > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to " > freebsd-current-unsubscribe_at_freebsd.org" >Received on Sun May 15 2016 - 14:16:25 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:04 UTC