On Apr 16, 2014 4:26 PM, "Miguel De Anda" <mig...@thedeanda.com> wrote: > > what's the sbo/slackware policy on commercial software? > > i've created a slackbuild for smartsvn (and i'll port it over for their git solution as well) but i'm hesitant to upload it. the script doesn't include any commercial or non-open source bits but the .info file would link directly to their binary. upon first launch it typically asks you to accept their agreement and choose from a feature-limited free (as in beer) version or to upload the license file. > > i create the build script simply because i wanted a launcher. > > regards, > miguel de anda > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > >
Should be fine. There are plenty of closed source and pay-for software packaging scripts in the SBo repository, and then there are pieces like the JDK where you have to accept a license agreement before downloading. Just don't distribute the software yourself - point to the original source and you'll be fine. --JK
_______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
