Spyke
linuxΒ·Linuxbypipe01

pear: a simple utility for listing file names inside archives

I made a small utility for listing the file names inside an archive file, e.g. tar, zip, etc. This comes in handy when you download some software package using the command line but you aren't sure whether to extract it in its own folder because you don't know what the file structure inside is.

pear: a simple utility for listing file names inside archiveshttps://github.com/pipe01/pearOpen linkView original on programming.dev
22
Comments10
π•½π–šπ–†π–Žπ–‰π–π–—π–Žπ–Œπ–
midwest.social

Huh. tar tf and unzip -l. I'm not sure I'd even bother to write a shell function to combine them, much less install software.

Zips just exploding to files is so common, if you just mkdir unzpd ; unzip -d unzpd file.zip it's going to be right nearly all of the time. Same with tarballs always containing a directory; it's just so common it's barely worth checking.

You write the tools you need, don't get me wrong. This seems like, at most, a 10-line bash function, and even that seems excessive.

function pear() {
case $1 in
  *.zip)
    unzip -l "$1"
    ;;
  *.tar.*)
    tar tf "$1"
    ;;
esac
}
17
pipe01reply
programming.dev

It only parses as little data as possible to get just file names, on some files like ZIPs it'll be just the header but on others like tar it'll have to walk through and seek to the start of each file. It should be pretty fast even on big files though

2
BrianTheeBiscuiteerreply
lemmy.world

Disagree on the .gitignore file. If you're the only developer and you only work off of one machine then it doesn't need to be committed. In a team setting it's absolutely imperative to commit it.

2
nousreply
programming.dev

You never want build artifacts to be committed. You don't want to have everyone working on your project to need to setup their own gitignore for every project. So it makes sense to have a common commited gitignore for files the project produces that should never be tracked by git.

I dislike when people put in editor files in the gitignore though. People should setup global ones for their local tooling.

1
BrianTheeBiscuiteerreply
lemmy.world

How do you ensure your teammates don't start committing their own IDE settings or committing "secrets.json" files or helper scripts or log files?

1
valareply
lemmy.dbzer0.com

So everyone who contributes to the project should make their own gitignore on every development machine they use to prevent committing build files, secrets ect?

I don't understand why you say it has nothing to do with the code when it literally has nothing to do with anything BUT the code.

What is the downside you see to committing the gitignore?

2
valareply
lemmy.dbzer0.com

Usually git add .

It's much faster, easier and less error prone to go with the blacklist approach of the gitignore file IMO.

1

You reached the end

pear: a simple utility for listing file names inside archives | Spyke