Petar,<br><br><div><span class="gmail_quote">On 8/10/07, <b class="gmail_sendername">Petar Petkoff</b> <<a href="mailto:tihomiroff@gmail.com">tihomiroff@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>I'm new in this list, so I'm not informed about your traditions and style.<br>Now I'm working on vlc compilation for slackware.<br>I can contribute all my work in this area, but I'm interesting from some
<br>points. Initially I started with simple config<br> ./configure --enable-release --prefix=/usr/local --enable-wxwindows \<br> --enable-debug --enable-v4l --enable-shared --enable-shared-pp \<br> --enable-pp --enable-gpl
<br>but I noticed that it is not suitable for me. <br>Looking around, i found a debian's config. I suppose that most of you prefer<br>to make own config, not to get it from debian or other distros, but this is<br>a good work for me. Currently I'm trying to work with slightly modified
<br>debians config, and I'm ready to share my considerations for these changes.<br><br>And here you can read my questions:<br><br>Q1. What should I do to make this slackbuild, when it requires some deps,<br>some of them are current cvs version :( - example - libmpeg2, ffmpeg? What
<br>should I do if the number of deps are 4-5 or more?</blockquote><div><br>We have discussed how to handle CVS snapshots previously. Please refer to the following archive: <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/2007-August/000590.html">
http://lists.slackbuilds.org/pipermail/slackbuilds-users/2007-August/000590.html</a><br><br>All dependencies must be listed in README<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Q2. What should I do to make this slackbuild compatible with <br>"non-totalitarian countries" and "totalitarian countries" due to patent<br>
problems?</blockquote><div><br>Take a look at one of my scripts to see the disclaimer I use: <a href="http://slackbuilds.org/slackbuilds/12.0/multimedia/speex/speex.SlackBuild">http://slackbuilds.org/slackbuilds/12.0/multimedia/speex/speex.SlackBuild
</a><br><br>Such disclaimer is aimed at the U.S. laws and since SlackBuilds.org is <br>located in U.S., this is an acceptable solution.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Q3. Is it preferred to split vlc package into some smaller packages or one?<br>for example: vlc and mozilla-plugin-vlc and etc.<br>or more: libvlc, vlc, vlc-doc, vlc-howto, mozilla-plugin-vlx and etc.</blockquote><div><br>
In my opinion, libvlc, mozilla-plugin-vlc, and vlc would be a good enough breakdown.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Q4. What should I do if compilation requires some header files only from <br>other package or lib, but this header files are not required for normal<br>working with compiled tool (Need only for compilation)?</blockquote><div>
<br>As mentioned above, all dependencies needed for either compilation, or day-to-day execution of the application need to be mentioned in README. You can specify which dependencies are permanent and which can be removed after the package is compiled.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'll note you, that I didn't read all documents, describing how to make a
<br>slackbuild package, so I prefer to read them instead of loosing your time.</blockquote><div><br>Here is a tutorial on how to write SlackBuilds: <a href="http://www.slackwiki.org/Writing_A_SlackBuild_Script">http://www.slackwiki.org/Writing_A_SlackBuild_Script
</a><br>Here is a general template: <a href="http://slackbuilds.org/template.SlackBuild">http://slackbuilds.org/template.SlackBuild</a><br></div><br><br><br>Best Regards,<br>Alex Lysenka<br></div><br>