I notice that I do not have virtuoso-opensource-utils installed. I ran yum info virt-o-u... and all it tells me is that these are utilities.
What would this package do for me? What commands, functions does it provide? What is in it that I might actually like to use or would conceivably use?
How do I get yum to tell me the above in the future, without me having to ask on a forum (for similar future cases when I wish to know what a package actually does, since yum info barely ever really tells you much at all upon which to base a should I/should I not install question on)?
On 07/22/2010 02:27 PM, Petrus de Calguarium wrote:
I notice that I do not have virtuoso-opensource-utils installed. I ran yum info virt-o-u... and all it tells me is that these are utilities.
What would this package do for me? What commands, functions does it provide? What is in it that I might actually like to use or would conceivably use?
How do I get yum to tell me the above in the future, without me having to ask on a forum (for similar future cases when I wish to know what a package actually does, since yum info barely ever really tells you much at all upon which to base a should I/should I not install question on)?
Something like this will show you what files are in the package without installing:
yumdownloader virtuoso-opensource-utils && rpm -qlp virtuoso-opensource-utils-6.1.1-1.fc13.x86_64.rpm
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Petrus de Calguarium wrote:
I notice that I do not have virtuoso-opensource-utils installed. I ran yum info virt-o-u... and all it tells me is that these are utilities.
What would this package do for me? What commands, functions does it provide? What is in it that I might actually like to use or would conceivably use?
My fault mostly for packaging it that way. Honestly, I don't know they are for or how they are used.
What I *do* know, if that they are not needed for the minimal virtuoso instance as required by nepomuk/soprano. But, I didn't feel comfortable just deleting or omitting them completely from packaging, opting instead to provide them in an option subpackage, presumably for those folks who do know what they are and how to use them. yes, lame on my part.
-- Rex
Thanks to both of you.
This answered my questions. I knew how to get rpm to tell me roughly what I wished to know and I see that this method just uses yum to download (very handy, since to use rpm to download you have to know the url).
2010/7/22 Patrick Boutilier boutilpj@ednet.ns.ca:
On 07/22/2010 02:27 PM, Petrus de Calguarium wrote:
I notice that I do not have virtuoso-opensource-utils installed. I ran yum info virt-o-u... and all it tells me is that these are utilities.
What would this package do for me? What commands, functions does it provide? What is in it that I might actually like to use or would conceivably use?
How do I get yum to tell me the above in the future, without me having to ask on a forum (for similar future cases when I wish to know what a package actually does, since yum info barely ever really tells you much at all upon which to base a should I/should I not install question on)?
Something like this will show you what files are in the package without installing:
yumdownloader virtuoso-opensource-utils && rpm -qlp virtuoso-opensource-utils-6.1.1-1.fc13.x86_64.rpm
On a side note the same can be achieved with "repoquery --list virtuoso-opensource-utils" which will do the same thing using repo metadata rather than downloading the package. repoquery is contained in the yum-utils.
On 07/22/2010 11:33 AM, Patrick Boutilier wrote:
Something like this will show you what files are in the package without installing:
yumdownloader virtuoso-opensource-utils && rpm -qlp virtuoso-opensource-utils-6.1.1-1.fc13.x86_64.rpm
repoquery -l virtuoso-opensource-utils
Rex Dieter wrote:
What I *do* know, if that they are not needed for the minimal virtuoso instance as required by nepomuk/soprano. But, I didn't feel comfortable just deleting or omitting them completely from packaging, opting instead to provide them in an option subpackage, presumably for those folks who do know what they are and how to use them. yes, lame on my part.
It's not lame. You did the right thing. People who want the utilities can install them. Most users don't need to know what they are for.
Kevin Kofler