[Slackbuilds-users] Slackbuild with Two Executables

[Brandon Pribula]

Thanks for the example, Jeremy :)

Although I've written shell scripts before these will be my first
slackbuilds and I'm second guessing everything (I guess want everything to
be perfect) so this example really helped.

On Tue, Mar 22, 2022 at 11:32 PM Jeremy Hansen <jebrhansen+SBo at gmail.com>
wrote:

> On Tue, Mar 22, 2022, 10:32 PM Brandon Pribula <b.pribs11 at gmail.com>
> wrote:
>
>>
>>
>> On Tue, Mar 22, 2022, 8:35 PM B. Watson, <urchlay at slackware.uk> wrote:
>>
>>>
>>>
>>> On Tue, 22 Mar 2022, Brandon Pribula wrote:
>>>
>>> > only options I can see are either splitting the package up into two
>>> separate
>>> > slackbuilds, or install both.
>>>
>>> > Which of those two options are preferable or is there another option?
>>>
>>> Other options:
>>>
>>> - Install both scripts in $PKG/usr/bin, call one "appname" and the other
>>>    "appname-posix", and explain the situation in your README.
>>>
>>> - Use an environment variable (APPNAME_POSIX=yes|no) to let the user
>>>    choose which of the scripts to include in the package.
>>>
>>> One thing that's *not* an option: Don't have one SlackBuild script
>>> that creates two separate packages (in other words, don't ever
>>> call makepkg twice).
>>>
>>> If you do decide to make separate packages for 'appname' and
>>> 'appname-posix', it'll have to be two separate SlackBuilds.
>>> Personally, I'd choose one of the other options (one SlackBuild, one
>>> package, either include both scripts or use the env to select one).
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>
>>
>> Thanks for the reply, B. Watson :)
>>
>> For the option of using an ENV variable, can it also be used to install
>> both scripts as long as makepkg isn't called twice?
>>
>> Then just use appname for the package name no matter which option is
>> chosen. In the README I could specify which executable to call depending on
>> the options chosen.
>>
>
> If you'd like to see an example of enabling different options, you could
> look at my mediainfo script. It defaults to build only the CLI, but you can
> enable the GUI with the CLI or do only the GUI.
>
> It'd be a little different since you're only dealing with scripts instead
> of compiling programs.
>
> https://slackbuilds.org/repository/15.0/multimedia/mediainfo/
>
> Jeremy
>
>> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220323/5f73e66e/attachment-0001.htm>