[Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir]
atelszewski at gmail.com
Sat Nov 5 12:09:00 UTC 2016
On 05/11/16 11:56, David Spencer wrote:
>> No YAML or XML needed to be written, just a simple syntax as proposed.
> Here's an offer.
> If *you* write all the code needed for slackrepo to parse that "simple
> syntax", and all the code needed for the user to select which options
> they actually want, and for slackrepo to remember them, and to make
> them happen when building, and do all that in a way that's compatible
> with slackrepo's existing configuration -- because slackrepo *already*
> has a 'hintfile' mechanism for selecting and remembering optional
> dependencies, and I genuinely did look at all the SBo READMEs to see
> what would work in the real world and to see what optional deps the
> default hintfiles should enable for lots of important packages -- then
> I'll consider merging it.
You don't have to actually implement anything other than skipping new
OPTIONAL field in .info.
At some point, if you decided you have the time, you then would go about it.
>> Is that really your proposal for all slackware-maintainers, or for all SBo-users?
> As I clearly wrote, it's for anybody who thinks they can design a
> solution like "OPTIONAL=". If you haven't checked how well the
> solution works for all the problems it's supposed to solve, you
> haven't finished the solution.
That is of course valid point, as with every good software design.
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
More information about the SlackBuilds-users