txtorcon 23.5.0

Jack Dangler tdldev at gmail.com
Fri May 19 09:30:16 EDT 2023


On 5/19/23 08:42, Benjamin Schollnick wrote:
>
>> *Top-posting? Really?
>
> In that case, yes, because the conversion did not depend on what was 
> originally said.  Unlike this conversation.
>
>> Actually, a very cursory look through the intarweb would have yielded 
>> this -
>
> And that’s the point, if you want to me to consider your package, I 
> should have some idea that it’s worth me investing more time into 
> seeing if it can help me.  As I mentioned simply stating that it was a 
> “Tor Control management API” would have been enough for me to say 
> “That’s not helpful to me”.  On the other hand if it said “Django 
> management API/Tool”, I would have gone to the git repository and 
> investigated.
>
> Effectively, posting a release notification is an *advertisement for 
> the package*, as well as a notice saying “*Here’s some updates”.*
> *
> *
> When done correctly, it can bring more people to use your package / 
> software…
>
>> While there are one or two graphical package managers (yumex and 
>> yumex-dnf that I know of), have a go at the cli manager(s) that may 
>> live on your distro and see if you can get pkg info about it. If 
>> you're not sure which one(s) you have, try these - Yum, Dnf, Rpm,Apt, 
>> Apt-Get, Deb, pacman, dpkg, and zypper for starters. *dpkg is my 
>> go-to pkgmgr of choice...
>>
>> Also, the names of many linux-centric utility plugins, extensions, 
>> and other goodies, while seemingly cryptic, are usually a prominent 
>> clue as to what the package is used for. The world of *NIX has never 
>> been for the faint of heart, but there are lots of very helping hands 
>> in its communities... :)
>
> This has nothing to do with package managers, this has to do with “Why 
> should I use this package” or “Should I use this package / software”. 
>  If the release notes are being send to people that don’t already have 
> the package then it’s worth the couple of sentences or a short 
> paragraph to allow someone that is unfamiliar with the package to be 
> able to see if they should investigate the package.
>
> Cryptic names maybe cute, but if they are not descriptive, then they 
> are not really that helpful other than being unique.
>
> - Benjamin
>
Yeah - um - I get the impression that there is so much going on that 
either I'm not qualified to respond to it, or I'd have to charge by the 
hour to unravel it, I'm just gonna leave this right here...


More information about the Python-list mailing list