[Slackbuilds-users] mplayerplug-in.SlackBuild

[Robby Workman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Niki Kovacs wrote:

> I just had some trouble building mplayerplug-in. After googling a bit, I 
> found the solution: mozilla header files for Slackware are contained in 
> the Seamonkey package. Only, my install is just a bare minimal desktop 
> (got a set of tagfiles for that) and doesn't include Seamonkey.
> 
> Maybe it's a good idea to mention it in the README.


Perhaps, but there's a slippery slope there - if we start mentioning
dependencies that are in a stock Slackware installation, then where
does that end?  Are we obliged to do that for all packages, or only
in cases where it's not obvious?  Who gets to decide what's obvious?

This of course is not my decision only, as we (the admin team) make
those as a team, but I am of the opinion that we should not start
this, as it creates the expectation of doing so for other scripts.

(CC'd to devel list)

- --

http://slackbuilds.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.2 (GNU/Linux)

iD8DBQFF34Co7QPvQNDlLwQRAhZQAJ9EbrcKRu1ctWKVkUySVf3XnnX0JwCfaoaW
VHJ+DBpEROS9P6KzylecDEs=
=GIOG
-----END PGP SIGNATURE-----