[Slackbuilds-users] Advice on making SlackBuilds obsolete

[Robby Workman]

On Tue, 25 Jul 2017 21:48:35 -0600
Erik Falor <ewfalor at gmail.com> wrote:

> Hello list,
> 
> I have finished updating a batch of SlackBuilds which I inherited from
> Ryan P.C. McQuen, and am seeking advice about how to deprecate some
> unnecessary SlackBuilds.
> 
> The Enlightenment project has consolidated their many libraries into a
> single source bundle. This means that the following 12 SlackBuilds
> are replaced by the upcoming efl.tar.gz:
> 
>     e_dbus
>     ecore
>     edje
>     eet
>     efreet
>     eina
>     eio
>     elementary
>     embryo
>     emotion
>     ethumb
>     evas
> 
> The situation for their Python bindings is similar. python-efl.tar.gz
> renders the following SlackBuilds obsolete:
> 
>     python-e_dbus
>     python-elementary
>     python-emotion
>     python-ethumb
>     python-evas


This is wonderful news!


> I have added a bit of text to the end of README explaining the new
> situation:
> 
> % tail -n4 README
> This package supercedes the following:
>     e_dbus ecore edje eet efreet eina eio elementary embryo emotion
> ethumb evas
> 
> Please remove the above packages before installing this one.
> 
> 
> Is there anything else that I should do to prepare the user for this
> situation? Is there a formal deprecation process that I should follow?


That sounds good, along with something similar for the python bindings.

Also make sure you leave a note in the Comments of the submission(s) to
remind us to remove them from our repo.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170725/4a38bc9e/attachment.asc>