What is the importance of `.gitignore` in AUR packages

[archbtw]

say i want to keep a copy of all my pkgbuilds in github repo after publishing it in the aur then having a .gitignore file is important or not.

#Ignore everything
*

#But not these files...
!.gitignore
!PKGBUILD
!.SRCINFO

EOS doesn’t have .gitignores in there builds:

GitHub - endeavouros-team/PKGBUILDS: PKGBUILDS for packages used in our...

but some do so i am a little confused:

GitHub - yochananmarqos/pkgbuilds: Personal PKGBUILDs

[dalto]

A .gitignore file describes a list files you don’t want to add to your repo.

For example, in the repos that I develop out of, I don’t want to upload temp files, editor autosaves or build files so I exclude those.

@archbtw

say i want to keep a copy of all my pkgbuilds in github repo after publishing it in the aur

The AUR is a git repo already so you don’t really have to do that.

[archbtw]

Yes you are right. I think that serves no purpose as i can always git clone the ssh link. I think eos does that so that others can collaborate and contribute. Can’t speak for yochanan though.

[archbtw]

@dalto What does this mean?

If you already have a package, initialize it as a Git repository if it is not one, and add an AUR remote:

$ git remote add label ssh://aur@aur.archlinux.org/pkgbase.git

Then fetch this remote to initialize it in the AUR.

If I want to make changes to a existing package on the aur. can i just git clone the ssh link, git add, commit and push?

[dalto]

@archbtw

If you already have a package, initialize it as a Git repository if it is not one, and add an AUR remote:

$ git remote add label ssh://aur@aur.archlinux.org/pkgbase.git

Then fetch this remote to initialize it in the AUR.

This is for new packages

@archbtw

If I want to make changes to a existing package on the aur. can i just git clone the ssh link, git add, commit and push?

Yes. As long as you are one of the maintainers.

Also, don’t forget to update the .SRCINFO if that is needed.

[archbtw]

Thanks Just one last. What is a label?

@archbtw

git remote add label

[archbtw]

@dalto

Also, don’t forget to update the .SRCINFO if that is needed.

already noted

Be sure to regenerate .SRCINFO whenever PKGBUILD metadata changes, such as pkgver() updates; otherwise the AUR will not show updated version numbers.

[dalto]

@archbtw

What is a label?

The name you want to call it.

[archbtw]

@dalto

The name you want to call it.

Call what? Because pkgbase would be replaced by the package name. So which name ?

[dalto]

It is the name you want to call the remote.

[moson]

I can tell you this one will haunt you at some point :

@dalto

Also, don’t forget to update the .SRCINFO if that is needed.

make an alias or script or something.
Otherwise you will definitely forget it at some point

updpkgsums && makepkg --printsrcinfo > .SRCINFO