Hi,
I know, but unfortunately Twitter on the CLI doesn't work as well as on the
GUI. I have used both Oysttyer and Rainbowstream on the CLI, but using Cawbird
on Linux GUI and Twitterrific on the Mac is simply a better experience overall.
I am not at all discounting Oysttyer or Rainbowstream, but fortunately I don't
have to. Often I would actually stay on the console, where I do a lot of my
actual work, mostly lesson planning, ironically for teaching Windows, where I'd
use mostly rainbowstream as my Twitter client.
Warm regards,
Brandt Steenkamp
Sent from my MacBook Air
Contact:
Phone: +27 (0)60 525 9181 <tel://+27605259181>
Email: brandt.steenkamp@xxxxxxxxx <mailto:brandt.steenkamp@xxxxxxxxx>
Twitter: @brandtsteenkamp <http://www.twitter.com/brandtsteenkamp>
On 29 May 2022, at 00:43, D.J.J. Ring, Jr. <n1ea@xxxxxxxx> wrote:
Oysttyer is a perl text twitter client. It works.
https://oysttyer.github.io/ ;<https://oysttyer.github.io/>
David
On Sat, May 28, 2022 at 5:26 PM Didier Spaier <didier@xxxxxxxx
<mailto:didier@xxxxxxxx>> wrote:
Hi Brandt and All,
Slint and Slackware packages are made with the command makepkg:
man makepkg
Generally this command is run inside a shell script called a SlackBuild.
Probably the best thing to do would be to contribute a SlackBuild for cawbird
to
https://slackbuilds.org ;<https://slackbuilds.org/>
Instructions to do so are here:
https://slackbuilds.org/guidelines/ ;<https://slackbuilds.org/guidelines/>
This per se is not enough to include the package:
- in Slackware proper as only Patrick Volkerding includes packages in
Slackware
(and he is generally reluctant to add new ones that he would then have to
maintain)
- in a package repository provided or at least supported by
https://slackbuilds.org ;<https://slackbuilds.org/> as there is none, per
their policy, see items #19 and
#20 in their FAQ:
https://slackbuilds.org/faq/ ;<https://slackbuilds.org/faq/>
For Slint, it depends. Generally I prefer that users build and install the
extra
packages using a SlackBuild available @ https://slackbuilds.org/ ;
<https://slackbuilds.org/>, using the
command line utility slapt-src or its GUI front-end sourcery but exceptions
can
be made on a case-by-case basis.
As an aside George Vlahavas aka gapan, maintainer of Salix has begun to feed
pre-built packages for Salix-15.0 in this repository:
https://slackware.uk/salix/x86_64/extra-15.0/ ;
<https://slackware.uk/salix/x86_64/extra-15.0/>
They are built using SlackBuilds from https://slackbuilds.org/ ;
<https://slackbuilds.org/>
Technically theses packages will be install-able in Slint-15.0 using slapt-get
or its GUI front-end gslapt, if /etc/slapt-get/slapt-getrc is edited to
include
this repository. I will consult with George to check the possible caveats.
In that case and if a cawbird SlackBuild is available in slackbuikds.org
<http://slackbuikds.org/> and if
George includes cawbird in this repository, you could install cawbird in Slint
with slapt-get.
As we say here:
Avec des "si", on mettrait Paris en bouteille. <smile>
deepl.com <http://deepl.com/> can help you translate it in English.
Cheers,
Didier
Le 28/05/2022 à 22:33, Brandt Steenkamp a écrit :
Hi all,===============================================================================
I was asked by the developers of the Twitter client Cawbird how they could
build
their software for Slackware and by extention Slint.
I, as many of you know, am not a developer, just a user who got tired of
Windows
and Microsoft's machinations, thus I really don't know how to help the dev.
If someone could send me a link to the relevant documentation, I would
really
appreciate it.
Also, once the software has been built for Slackware, how would the
developers
get it in the repo?
The Slint mailing list.
Archive: https://www.freelists.org/archive/slint ;
<https://www.freelists.org/archive/slint>
To subscribe or unsubscribe, email slint-request@xxxxxxxxxxxxx
<mailto:slint-request@xxxxxxxxxxxxx> with the subject
'subscribe' or 'unsubscribe', then answer the email you will receive.
More: email slint-request@xxxxxxxxxxxxx <mailto:slint-request@xxxxxxxxxxxxx>
with as subject 'help' or 'commands'.
