[Slackbuilds-users] Advice on making SlackBuilds obsolete

Erik Falor ewfalor at gmail.com
Wed Jul 26 03:48:35 UTC 2017


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


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?

Thanks,
-- 
Erik Falor
Registered Linux User #445632                    http://unnovative.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170725/fcd276b1/attachment-0001.asc>


More information about the SlackBuilds-users mailing list