[Slackbuilds-users] Package name change: how to proceed

[Willy Sudiarto Raharjo]

> I maintain two packages one named obnc and the other obnc-libstd. The
> first is an Oberon compiler and basic library and the second is a
> library for it with extra functionality. The author of the compiler has
> decided to rename second from obnc-libstd to obnc-libext.
> 
> How should I proceed? Should I make a new SlackBuild named obnc-libext
> and request the removal of obnc-libstd?

You can keep the same name if you like or submit a new name and leave a
comment section  to remove the old name.

> Additionally, I wanted to ask which is the correct way to proceed when
> using the mirror of Slackbuilds on github
> (https://github.com/willysr/slackbuilds). Is the correct way fork that
> repository, make changes and then do a pull request? Is this better
> (easier) for the team maintaing Slackbuilds.org than submitting the tar.gz?

It's better to send PR/MR through this repositories:

https://github.com/SlackBuildsOrg/slackbuilds/
https://gitlab.com/SlackBuilds.org/slackbuilds/

Both submission and PR/MR works fine with us

-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190202/a973c87f/attachment-0001.asc>