[Slackbuilds-users] Packaging questions

[King Beowulf]

On 3/20/20 2:36 PM, Didier Spaier wrote:
> Le 20/03/2020 à 21:25, B Watson a écrit :
>> On 3/20/20, Didier Spaier <didier at slint.fr> wrote:
>>> Hi,
>>>
>>> I intend to upgrade espeakup, dynamically linked to espeak-ng not
>>> espeak, as speech is then way better (tested by Slint users).
>>>
>>> Indeed I will provide a SlackBuild for espeak-ng but that leads to a few
>>> questions.
>>>
>>> For both espeakup and espeak-ng I do a "git archive <commit>".
>>>
>>> 1. How should I name $VERSION? git<commit>, <commit>, git_commit?
>>
>> epeak-ng version 1.50 was released 4 months ago, is the latest git really
>> that much better than the release? If not, I'd stick with the release.
> 
> Thare have been several fixes that worth an upgrade, I think. And the
> version I consider is already used in Slint since two weeks with no
> reported issue (I have explicitly requested a feedback), both in console
> mode through espeakup and in graphical environments through speech-dispatcher
> and Orca.
> 

If the size of the fixes aren't too large, you can just include those
patch(es) in the script tarball and have your script patch the source in
the fly.  Then you won't need to host the source code somewhere.

-Ed


-------------- 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/20200320/758b9e2a/attachment-0001.asc>