I never really entirely understood what you meant by key:value, could you
provide an example? :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/107#issuecomment-305873269_
Closed #107.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/107#event-976010362___
Rpm-maint mailing list
Rpm-maint@lists.rpm.or
As long as high end tools cannot be sure that the data they are looking at are
actually the ones they are interested in but some random, similar looking data
added for a completely different purpose, this is of no use. Closing.
--
You are receiving this because you are subscribed to this threa
2017-01-26 15:28 GMT+01:00 Florian Festi :
> While I have some sympathy for the idea as such I think just putting
> random stuff in a tags is a bad idea. We should at least force some
> key:value structure. This way someone parsing the tags has a fair chance of
> filtering out the entries of inter
While I have some sympathy for the idea as such I think just putting random
stuff in a tags is a bad idea. We should at least force some key:value
structure. This way someone parsing the tags has a fair chance of filtering out
the entries of interest without other data littering the results.
Whi
About suse patterns: in the old days(tm), they were pretty similar to comps.
Nowadays they are just rpm packages with standard dependencies. You shouldn't
try to judge them by looking at that messy spec file.
--
You are receiving this because you are subscribed to this thread.
Reply to this ema
On 12/12/2016 06:13 PM, proyvind wrote:
Skimming through your link to suse's patterns, it's hard to easily grasp
it's purpose, while if serving the same purpose, the implementation of
is not only extremely confusing, hard to maintain and extremely
non-standard fashion, rather than implemented in
@proyvind @proyvind, I still didn't got use-case for this. Can you show some
example?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/107#issuecomment-266473326
Skimming through your link to suse's patterns, it's hard to easily grasp it's
purpose, while if serving the same purpose, the implementation of is not only
extremely confusing, hard to maintain and extremely non-standard fashion,
rather than implemented in rpm itself in a proper, intuitively nam
I'm a bit confused. What exactly are MetaTags supposed to do? You mention
comps, are these supposed to be more like [SUSE's
patterns](https://build.opensuse.org/package/view_file/system:install:head/patterns-openSUSE/patterns-openSUSE.spec?expand=1)?
I can't quite tell what this is supposed to d
@proyvind pushed 1 commit.
cfe0869 MetaTags: should be translatable
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/107/files/8d0a541248e136b1ebcdec93ae4a2d5b9924882d..cfe0869f08b5d0248c4b19e4da29a0eddd
@proyvind pushed 1 commit.
8d0a541 update tests with METATAGS added to queryformat test
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/107/files/7b838c4eb22c5df3b9a0c308cbe311d8764118c0..8d0a541248e136
Erm, how comps are related to this?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/107#issuecomment-265371083___
Rpm-maint maili
Can one of the admins verify this patch?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/107#issuecomment-265370455___
Rpm-maint
Maintenance of multiple meta tags for packages outside of packages, replacing
optional group tag isn't ideal wrt. package maintenance scaling..
In stead a MetaTags: tag has been added, accepting multiple tag words.
This seems like a far more ideal solution than what's currently implemented
with
15 matches
Mail list logo