Re: adding different compression types to createrepo
seth vidal <[email protected]> Thu, 05 Aug 2010 11:31:45 -0400
| Newsgroups | gmane.linux.rpm.metadata |
|---|---|
| Message-ID | <1281022305.1345.241.camel@oliver> |
On Thu, 2010-08-05 at 11:26 -0400, Robert Xu wrote: > On Thu, Aug 5, 2010 at 11:12, seth vidal <[email protected]> wrote: > > On Thu, 2010-08-05 at 09:05 -0600, Matthew Dawkins wrote: > >> > > >> > >> OK. I'll try to add the "Requires(hint):" to the sqlite > >> as well. > >> > >> > >> > >> It should only be an extra column of "hint BOOLEAN > >> DEFAULT FALSE" > >> > > > >> > > The requires(hint) you're talking about - do you mean the > >> requires > >> > > (pre) > >> > > information? If so - that's stored in the sqlite db. > >> > > >> > It's for RPMSENSE_MISSINGOK, suggests/enhances hint. > >> > > >> > And yes, it is stored similarly to RPMSENSE_PREREQ > >> > >> > >> Ah - missingok, that's special to only specific rpm versions. > >> > >> > >> To rpm5??? which is another progressive project that we support and > >> would like to see better supported with createrepo. > >> > > > > rpm5 is a fork and one I do not and will not be supporting anytime soon. > > > > I want nothing to do with it and that's really the end of the > > discussion, imo. > > > > the tone doesn't really help the situation here. The tone reflects reality and a far deeper history than I want to go into here. But more to the point - since the python bindings between rpm and rpm5 have diverged compatibility is no longer guaranteed. Yum and createrepo will be following rpm. -sv