Hi list members,<br><br>I know this is FAQ no 14, and I know all the technical and political issues of the <br>"dependecy problem", but...<br><br>The current rule of this slackbuild project is that we can put the "informal"
<br>list of dependencies into the README file.<br><br>Supposing that most of us have a full slackware install on our machines,<br>is it a very bad idea that a package lists those dependencies formally which are <br>solved by the slackbuilds project?
<br>For example we can put "SBODEPS=pkg1,pkg2" os something similar to the .info file.<br><br>The reason is that I would like to write a script to<br>1. to compile an application automatically, building its sbo deps before
<br>2. I would like to write a script which checks which packages have to be rebuilt, when <br> an other package releases a newer version. I know this later is harder because I have<br> to know that I really need a rebuild or not. (when I have a newer .so lib it does not
<br> necessary need to rebuild of its dependant)<br><br>So the first target is 1.<br><br>If we do not want to put it to the .info the second choice is to put it to the README as now, <br>but in a standard form (in a separate line by a leading token) to able to parse by grep or
<br>similar tools.<br><br>Sorry if it was discussed later!<br><br>thanks for your tolerance,<br>feco<br>