Linux

9406 readers

478 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

pear: a simple utility for listing file names inside archives (github.com)

submitted 1 day ago by pipe01@programming.dev to c/linux@programming.dev

14 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] Lembot_0004@discuss.online 0 points 1 day ago (1 children)

It just isn't. It has nothing to do neither with code nor with compiling. The same tier of "partness" as /etc/fstab or something.

[–] vala@lemmy.dbzer0.com 2 points 1 day ago (1 children)

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?

[–] Lembot_0004@discuss.online 1 points 1 day ago (1 children)

You commit with add -A? Well, ok.

[–] vala@lemmy.dbzer0.com 1 points 1 day ago

Usually git add .

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