[opensuse-packaging] Lack of information
Hi, what I really miss sometimes is the information which toolkit or desktop environment an application is for. Qt, GTK, CLI Sometimes I want to know if it is a compiled application or just a script. Binary, Python, Perl, Ruby It would be nice if such things would be in the description or some extra fields. Maybe the software portal or zypper is able to get the information from the requires. The software portal could show little icons and zypper could print it in the deatailed view. Just some wild thoughts... -- andreas
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/04/2009 11:05 AM, Andreas Schneider wrote:
what I really miss sometimes is the information which toolkit or desktop environment an application is for.
Qt, GTK, CLI
Sometimes I want to know if it is a compiled application or just a script.
Binary, Python, Perl, Ruby
It would be nice if such things would be in the description or some extra fields.
Maybe the software portal or zypper is able to get the information from the requires.
We could certainly guesstimate which environment it is for by analyzing the Requires of a package, indeed. We are currently not parsing+storing Requires nor Provides, but it can be added. We'll have to add Provides support anyway, for another feature. Detecting whether it's a script or a compiled binary is somewhat more difficult, because you often end up with packages that contain both. But if it doesn't require glibc and instead requires some shebang, then, yes, it is a pure script. Which shebang is required could then be used to detect whether it's python, bash, perl, ruby, or whatnot.
The software portal could show little icons and zypper could print it in the detailed view.
Yes, feasible in theory. Time to implement is another issue ;)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
Am Montag 05 Oktober 2009 schrieb Pascal Bleser:
Detecting whether it's a script or a compiled binary is somewhat more difficult, because you often end up with packages that contain both. But if it doesn't require glibc and instead requires some shebang, then, yes, it is a pure script. Which shebang is required could then be used to detect whether it's python, bash, perl, ruby, or whatnot.
Which reminds me, that there's a lot of confusion in our packages, whenever I look into shebang arguments. While rpmlint warns about non executable shebang scripts, it doesn't check, if they're valid. Sure, creating that parser is going to get tough, though... Pete -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (3)
-
Andreas Schneider
-
Hans-Peter Jansen
-
Pascal Bleser