[Slackbuilds-users] [ANN]: sbo-dev-helper project
niels.horn at gmail.com
Thu Dec 17 09:32:11 UTC 2009
On Thu, Dec 17, 2009 at 3:21 AM, Robby Workman <rworkman at slackbuilds.org> wrote:
>> > - I think the solution to add files can be improved. I have several
>> > SlackBuilds with extra files (patches / README.Slackware / etc.). I
>> > suggest adding everything to the tarball, *except*: *.tar.?g* / *~ /
>> > <other_backup_files>
>> Hmm, my hobbit is untar the source in the working directory and have
>> a look at it and write/modify the SlackBuild etc. And the working dir
>> maybe really dirty -- have log files, swp files, and other files that
>> shouldn't be in the tarball. So I prefer the "white list" approach
>> than the "black list" approach. What do you think?
> Both methods are failure prone. While a whitelist is *usually*
> the best solution, I don't think it is in this case - there's
> simply no way to predict the names of files that should and/or
> should not go into the tarball. In fact, there may even be
> some legitimate cases in which a tar.gz archive should be included
> in the tarball (even though I'm not aware of one at the moment).
> I know the Slackware source tree contains several such tarballs
> inside source directories, but thus far we've not found a need
> for them (to my recollection).
I have one SlackBuild in pending that contains a tarball - one with
several patch files for libvmime supplied by the zarafa authors.
> Ultimately, I think it should be up to the potential submitter
> to ensure that the archive which he/she plans to submit contains
> all (and only) the files it's supposed to contain. If some
> "helper" can't do this reliably (and I posit that it cannot,
> as this task simply *requires* human interaction), then don't
> try to build such functionality into the helper.
Like I said in my first mail, I tried to write some "helper" scripts
as well, like a sanity-check (same "VERSION" / "PRGNAM" in info &
SlackBuild, etc.) and I choose the "blacklist" approach for creating
the tarball. I only go one level deep (so that I do not include
untarred sources) and exclude any tarball (so it did not work with my
own libvmime SlackBuild mentioned above) and any backup (*~) files.
With the one exception above, it worked fine until now (but is a very
ugly script :D )
I should filter *.log files as well, as I sometimes create them...
More information about the SlackBuilds-users