Pre-devlog notes

Yes, this is how I do my devlogs now. I want to take advantage of all Stardance’s new devlog features to make them a bit neater.

Also, this may be my first time I made a commit to easyAPT’s Github repository in, like, 2 weeks. I just decided to take a break from coding for a little bit.

Actual Devlog 6

We went from I forgot the other version and the GitHub commit history has missing info for some reason to JUN30-V32.

What changed?

I have changed a good amount of things with easyAPT, including…

• The version system instead of organizing them by what versions were released on what day, I organize them by the date that they were released and the overall version (eg, JUN9-R7 to JUN9-V20). V, in my case, means revision number.)
• The updating tool 90% bug fixed
• Case $? in errors I made this mistake a lot. In case statements, which I use a ton of, you have to use case “$VARIABLE” in or case “TEXT” in, not case $? in, or it’ll always assume the last option. Take this sample code as an example,

#correct
case "$?" in
            0)
                    echo "Success"
            *) 
                    echo "Failure"
esac
#This code displays the right end result for a command. But my mistake was
case $? in 
           0)
                   echo "Success"
            *)
                   echo "Failure"
esac
#Which always assumes it fails, every time, even if $?=0.

Thanks to Vim (the super useful editor that’s my new favorite), what would’ve taken hours took a split second.

How close am I to my first GitHub release of easyAPT?

Pretty close now. All the options menu work fine. When I paste the final contents into easyAPTmenu.sh, then this project will be pretty much finished and ready for anyone to demo. But, there’s still a bunch of bugs I need to fix.

What’s next for easyAPT?

There’s a lot of planning for what’s up next.

• Case statement bug fixes I turned on a Vim feature that highlights some lines red if there are syntax errors. For some reason I haven’t figured out yet, most, if not all, of the ;;s and the esacs in my script are highlighted red. I haven’t experience bash stop the script due to syntax errors, so I’m going to have to look through the code and maybe do research.
• About menu option Takes a few seconds to code. Just a nice little inclusion telling the user who made it, the current version, and possible licensing info (if we get to that stage)
• More bug fixes I’ll test every single possible option before pasting the menu part into another script.
• Making ./easyAPTmenu.sh hidden I’d like to turn easyAPTmenu.sh into .easyAPTmenu.sh. It may seem like a small change, but adding a dot to the beginning hides the file by default, like if you typed “ls”. This is the case for the version files as well as others used for Github and Wakatime.
• Anything else Things will get added and removed from here as releases go.

Thank you for reading! If you have any questions, comments, or recommendations, please let me know!