SBo Protocol for using slackware-current package as slackbuild dependency?
 

Suppose I am writing a slackbuild (with a view to submitting it to SBo) and as a dependency it has a library which is in slackware-current but not slackware-14.0 (the -14.0 version is too old).

Does anyone know if there is there an established way of indicating this? Maybe:

1. just have this explicitly stated in the ``This requires'' field, i.e. ``create/obtain lib-whatever from slackware-current and use upgradepkg'';
2. also provide a separate SBo slackbuild, possibly copying exactly from slackware-current/source/*/ and crediting Pat appropriately;
3. something else?

I couldn't see anything along these lines after a quick look through the SBo FAQ.

Cheers,

Michael

FAQ 15: For what version of Slackware are these scripts designed? Will they work on newer versions?
All of our scripts should work with the most recently released version of Slackware; if this is not the case, you should file a Bug Report. Except as noted in the next FAQ entry, the scripts should also work on older versions of Slackware. Slackware -current is not supported, but as a general rule, the scripts should work on it as well.

###

Additionally, SBo does not accept scripts for things included in Slackware. So I think you'll need to wait for -current to be released as 14.1 or whatever and the SBo scripts to be updated for the new release.

Thanks chess. Actually looking into it a little deeper, at the very bottom of their Submissions page http://slackbuilds.org/guidelines/ it says:

"As a general rule, we do not accept SlackBuild scripts of software that is included as part of Slackware; however, exceptions may be made by the admin staff on a case-by-case basis."

So they may in fact accept a slackbuild of something in slackware-current. In that case it seems folly to deviate from Pat Volkerding's own slackbuild (unless of course that causes some problems to slackware-14.0). I could imagine putting a comment in somewhere saying "this software, which is in fact included in slackware-current at the present time is only provided so package such-and-such will function in slackware-14.0" or something along those lines.

If I don't receive any guidance from a SBo maintainer here I'll pursue it with them directly, or else just submit something and see what they say then.

Cheers,

Michael

I think mozilla-firefox-esr is a good example
They are already included in Slackware, but they are also placed on SBo since the one in Slackware is a rolling release from Mozilla

Thanks very much Willy, I hadn't seen that and it is very helpful to know it is there and see how it is ``packaged''.

Cheers,

Michael

Michael, I would jump into #slackbuilds on IRC or post on the ML.

The SlackBuilds.org policy is that you have to supply all missing dependencies for a script that you submit. Any script on SlackBuilds.org should result in a working package, with no other requirement than a full installation of Slackware and other scripts found in the SlackBuilds.org repository.

If you need to add a script for a package which is in -current but not in 14.0 you can write your own SlackBuild for that and submit it, or use the SlackBuild which is part of Slackware-current - but then ask permission first from Patrick, it is the proper thing to do. And do not change the copyright lines of the script in that case!

Eric

Thanks Eric, I had come to a similar conclusion about what ought to be submitted, but it was a bit unclear what would and wouldn't be ok re: one of Pat's own slackbuilds from -current. If and when I am ready to submit something I'll be sure to contact Pat first.

Cheers,

Michael