![]() ![]() We can now import the upstream version into our packing source code by using the file downloaded from wget before. Everything is empty we have a clean working area. :~/kali/packages/instaloader$ git logįatal: your current branch 'master' does not have any commits yet Nothing to commit (create/copy files and use "git add" to track) If we wanted to, we can confirm this by looking at “status” and “log”: :~/kali/packages/instaloader$ git status Initialized empty Git repository in /home/kali/kali/packages/instaloader/.git/ We are now going to create a new blank git repository: :~/kali/packages/instaloader$ git init We need to switch paths to the working location of the package: :~$ cd ~/kali/packages/instaloader/ However, it is preferred to use a tag release when available. If there isn’t a tag release for the software (or it hasn’t had an release in some time), we can use the latest git commit. We will use wget and make sure to format its name appropriately according to Debian’s standards for source packages (take note of. Here is the option to download instaloader-v4.4.4-windows-standalone.zip, as well as Source Code (zip), and Source Code (tar.gz). Going to the GitHub’s release page, we can see the latest version (which at the time of writing is 4.4.4). However, this will be covered in another guide. If we were updating a package (and it was packaged correctly), there is a process to help speed it up. upstream/ will be a compressed file of the source code of the application (ideally from a tag version release which we saw before)īecause we are making a new package from scratch, we’ll manually download the version of the tool we want to package up.packages/ will be a source code of the package we are going to create.Let’s set up our directories now for this package: :~$ mkdir -p ~/kali/packages/instaloader/ ~/kali/upstream/Įverything that relates to us building a package will be using ~/kali/. We will assume that we have already followed our documentation on setting up a packing environment. We’ll be digging into each of these more later, for now it is just information to know. What we notice here is some information that will come in handy later: A few things stand out which we take a note of: The first thing we do is look at the application’s GitHub page. Because of the learning opportunities and simplicity, this makes it a good introduction package. This makes it a relatively simple package, however not as straightforward as only packaging up a shell script would be. Instaloader is a Python 3 application with a single dependency (Python’s requests). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |