Quote:
Originally Posted by Daedra
(Post 4393751)
I maintain the conky script and it may beyond you, but like were saying audacious is standard in the stock Slackware full install, which most people here seem use. Why would I gut a useful feature out of the build script when its easy enough for people who don't need it to just edit the script themselves. It takes maybe an extra two minutes to build it by hand vs. sbopkg. Is it really that inconvenient for you?
|
I apologize if my comment seemed like the `flamewar' type - such was not my intention. I would first commend you for maintaining the script in the first place. What I was trying to elucidate was that I find it unusual that audacious is a
mandatory dependency of conky, since it is not
necessary for conky to function (why I say `mandatory' is revealed later in the post - please see below). I concede that it is included in the regular Slackware stock build, but whether a person actually chooses to have it on their system is a matter of personal choice. Just to corroborate my point, if you take a look at
this thread over in the Arch Linux forums representing a poll of media players, most people use mpd as opposed to audacious, whereas mpd is not a mandatory dependency of conky, though the flag is indeed enabled by default in your script, which detects mpd if it is there and not otherwise. Agreed that mpd is not part of the standard install, but there are tons of packages in Slackbuilds.org that have external dependencies not in the Slackware default install. I am
not making this a case to make mpd a dependency - I would just like to ask: why not the same for audacious? Leave the flag enabled, and if the user has it, include the support, else not. Listing it as a mandatory dependency requires modifying the script itself, which though not really inconvenient because it entails editing a few lines of code, is an extra step. If one were to argue that Slackers are 'advanced' enough to deal with that, then one could also say that they are advanced enough to just download the source themselves, and './configure + make + make install' themselves, thereby eliminating the need for the entire Slackbuilds.org repository, which would be a ludicrous statement! But, as I acknowledged, the choice is indeed yours.
Quote:
Originally Posted by abrouwers
(Post 4393787)
Actually, the problem is that YOU built it against audacious, and then removed the audacious package. Otherwise, your package would not have linked against audacious in the first place. Don't blame the tools :-)
|
To that I can only reply - you did not read my last post carefully. I am not here blaming the tools. I
also tried after I
purged audacious, and when I purge conky and try reinstalling it via sbopkg, this is what I get:
Code:
checking for Audacious... configure: error: Package requirements (audacious >= 1.4.0 audclient dbus-glib-1 glib-2.0 gobject-2.0) were not met:
No package 'audacious' found
No package 'audclient' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables Audacious_CFLAGS
and Audacious_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
conky:
Would you like to continue processing the rest of the
build queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.
(Y)es to continue, (N)o to abort, (R)etry the build?:
This therefore implies that audacious is listed as a mandatory dependency, and not merely as a flag which is harmless even if enabled in the absence of audacious. Like I said, it doesn't really bother me to either leave audacious installed or build with it explicitly disabled. I was merely pointing out that turning on a package as a mandatory dependency which is not really
needed for the functioning of the package being installed is an anomalous choice.
