On 10 August 2017 at 01:41, Willy Sudiarto Raharjo
<will...@slackbuilds.org> wrote:
>
>> So I submitted a new version of the vulkansdk SlackBuild and I noticed
>> the following:
>>
>> slackware-current has since added a package for the Vulkan SDK. In
>> -current, the package is named "vulkan-sdk". The SBo SlackBuild is
>> named "vulksansdk" and it builds a package by that name.
>>
>> Should I do anything about that, or should I just leave it
>
> You can leave it as it is.
> We will remove it on next devel cycle as it is included in -current now along 
> with some other scripts

Note that automatic dependency managers will not be able to pick up
that on -current there already is a vulkansdk since it's named
differently.

/ Andreas
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to