Page MenuHomeSolus

tdrop
Closed, ResolvedPublic

Description

Name of the software: tdrop

Project/product Homepage: https://github.com/noctuid/tdrop

Why we should include this into the repository, i.e. what does it do that the alternatives do not?

It is a convenient way to make pretty much anything like a dropdown terminal. Example usage:

  • Make your favorite non-dropdown terminal or any graphical application into a dropdown application or really, even better, make it spawn in an exact position on the screen every time.
  • I'll use it for my calculator of choice 'speedcrunch' on a hotkey and adventures on my spare laptop on bspwm and sxhkd.

For further reasons on why tdrop is such a fantastic software see the first section on the github page "Advantages Over Other Dropdown Terminals" - a straight no nonsense list on supported features, clear and consice. Thought it was redundant to copy and paste it into this here post.

The github is really well filled with documentation on why, how and usage.

Is it open source?: Yes under BSD 2-Clause "Simplified" License: https://github.com/noctuid/tdrop/blob/master/LICENSE

If it is open source, please provide a link to the most up to date, versioned source tarball/zipfile. master.zip links will not be accepted.: https://github.com/noctuid/tdrop/releases - I asume a direct link to tarball/master.zip is not accepted but the release page is acceptable? Otherwise I'm not sure what to provide.

If there are no upstream releases but the inclusion policy is otherwise met, please provide a link to the source repository (i.e. GitHub): That's where it lives.

Event Timeline

linkert created this task.Dec 6 2019, 8:15 AM

Not really sure why we would need to package this when literally it's just a bash script. Surely something you could just download?

linkert renamed this task from [Request] tdrop to tdrop.Dec 6 2019, 9:41 AM

Not really sure why we would need to package this when literally it's just a bash script. Surely something you could just download?

See, it did not occur to me that this is just a bash script at all - news to me :) Have used it on Void where it's present in the repos. I'm not comfortable with changing the PATH variable or whatever it's called and putting the script in the right location and then setting the permissions with chmod. Don't get me wrong, it's not a huge issue and I'll do it if I have to but it still would be easier for most to simply go:

eopkg install bspwm sxhkd tdrop ....

done, got it use it.

It's under development, currently at 0.3 and it has moved forward since I last used it. If I downloaded it I'd have to either be fine with the version I downloaded and miss out on any future updates or keep my eyes on the github for updates. Sadly I'm not a dev and I'm uncomfortable with package maintenence and I appreciate what package maintainers do - that said it would probably (without actually knowing) be quite an easy package to maintain right? Not like say Blender that I've come to understand relys on Python 2 which is supposedly a pain to update and maintain and is the reason it's stuck on 2.79b on many distros ~6 months after the release of 2.8.

Maybe this is the perfect time for me to shine as I guess this would be easy to maintain due to being a simple bash script and it's dependencies probably already is installed on Solus?

I think it would be of joy to quite a few people and not be much of a load to whoever ends up being the maintainer. I did look into package maintaining on void but was greeted with a bit of RTFM-"you are more of a burden than help"-attitude which bummed me out and made it no easier getting into it.

JoshStrobl added a comment.EditedDec 6 2019, 10:30 AM

If I downloaded it I'd have to either be fine with the version I downloaded and miss out on any future updates or keep my eyes on the github for updates.

Yea that's fair.

Maybe this is the perfect time for me to shine as I guess this would be easy to maintain due to being a simple bash script and it's dependencies probably already is installed on Solus?

Yep! Because it's just a bash file and a man page, there isn't any compiling necessary, only the use of our %make_install macro (basically sets DESTDIR, documentation available here with the category being here), so it should be a pretty simple package to start getting into Solus packaging. Though an aside, their Make install step installs a LICENSE file. That isn't necessary because our package.yml license key specifies the license, so that file can be nuked from $installdir.

I did look into package maintaining on void but was greeted with a bit of RTFM-"you are more of a burden than help"-attitude which bummed me out and made it no easier getting into it.

Sorry to hear, we try to avoid that sort of attitude.

Until I finish the new Help Center (which will have a quick start guide), my advise would be to follow the rough path of:

  1. Setting up Packager File, Initializing Solbuild, and Setting up common documentation available on our Building a Package page.
  2. Setting up arcanist, which is what we use for patch management via Phabricator. Documentation available here.
  3. Generating the initial package.yml in a new tdrop folder by following the Generating a Package.yml documentation here. The majority of the specification for our macros, metadata, etc. are in the Package.yml page (linked earlier re. DESTDIR) bit.
  4. Building the package (see the Building a Package page linked in step 1).
  5. Package submission and review via the "Submitting a Package" page I linked in step 2.

At the moment the documentation is a bit scattered across different pages, that'll get sorted with the Help Center redesign (which also reorganizes our open source Help Center documentation).

If you have any questions, feel free to join #Solus-Dev on irc.freenode.net with the pre-installed IRC client (Hexchat or Konversation). Note you'll need to register with the freenode service if you haven't already, this is for spam protection reasons.

JoshStrobl triaged this task as Normal priority.
JoshStrobl moved this task from Backlog to Accepted For Inclusion on the Package Requests board.