Re: adding different compression types to createrepo
Matthew Dawkins <[email protected]> Wed, 4 Aug 2010 12:01:45 -0600
| Newsgroups | gmane.linux.rpm.metadata |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Aug 4, 2010 at 11:47 AM, seth vidal <[email protected]>wrote: > On Wed, 2010-08-04 at 11:30 -0600, Matthew Dawkins wrote: > > > Like Robert Xu said. Let the distros hash out what format and > > compression they want to provide in their own repos and not let one > > person or distro make that decision for us. If in time your sqlite > > format is AWESOME, I'm sure we will switch, but until that time we > > will continue to use the xml files. > > > > > That's the problem. RPM just had xz/lzma support added for compressing > payloads. That broke..... all older versions of rpm being able to even > read/handle packages made by the newer versions. > > I was hoping to keep from doing that to all of our users AGAIN. > > I would LOVE to be able to wish-away all backward compat issues, but > they exist and they ARE REAL. > > So, if we're going to add code that breaks compat with older clients, > I'd rather: > > - make BIG changes that benefit us a lot more than just changing the > compression format > - work on a new standard. > > -sv > > So you are saying you would purposely using the xz switch? In my case I have no problems using it. Smart supports the decompression of xz'd xml files. It's not even the case of me breaking backwards-compat repo. Adding an option and using it are two separate issues. _______________________________________________ Rpm-metadata mailing list [email protected] http://lists.baseurl.org/mailman/listinfo/rpm-metadata