[CentOS] Re: Mixing RPMforge and EPEL (Was: EPEL repo)
Dag Wieers
dag at wieers.comTue Jul 31 20:28:39 UTC 2007
- Previous message: [CentOS] Re: Mixing RPMforge and EPEL (Was: EPEL repo)
- Next message: [CentOS] Re: Mixing RPMforge and EPEL (Was: EPEL repo)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, 29 Jul 2007, Rex Dieter wrote: > drew einhorn wrote: > > > Dumb question. > > > > Can't we identify the source of the package by looking at the signature. > > Signature, vendor, etc... right. Pretty much why epel (so far) didn't see > the need/value in the complexity/overhead of introducing repotags. That information is not shown by yum on dependency failures (which break yum). Not having that information in copy&paste output requires people to ask one or more questions before finding the cause and redirecting to the correct forum. Having that information available in the output (which is impossible with the signature or vendor because of the size of the string) will make it apparent to the user having the problem where to report a problem. Besides, what complexity/overhead does the repotag have exactly ? But we all discussed this over and over again, just to be rebutted by the same false arguments or saying that RPM can be changed. (which it can NOT for the foreseeable future ! thank you very much) -- dag wieers, dag at wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors]
- Previous message: [CentOS] Re: Mixing RPMforge and EPEL (Was: EPEL repo)
- Next message: [CentOS] Re: Mixing RPMforge and EPEL (Was: EPEL repo)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list