reading "Build Files Exist" seems to suggest the package already exists, but it's not, I think.
So what is "CleanBuild" and what do the options mean: [N]one [A]ll [Ab]ort [I]nstalled [No]t Installed
And is meant by (1 2 3, 1-3, ^4) ?
reading "Build Files Exist" seems to suggest the package already exists, but it's not, I think.
So what is "CleanBuild" and what do the options mean: [N]one [A]ll [Ab]ort [I]nstalled [No]t Installed
And is meant by (1 2 3, 1-3, ^4) ?
lets start with why you are getting this output: If you see a screen like this your app is pulled from the AUR. The AUR works different from the other repos. While the normal repos download standardized arch packages in the form of tar-archives the AUR takes a more radical approach: get the app on your system by (almost) any means necessary. So the AUR doesn't contain a package but a text file containing instructions. Where to download the necessary files, where to put them, that sort of stuff. In most cases the files is just the source code and your system will compile it according to the instructions in that text file. Compiling means it will turn the human readable programing in to computer readable stuff. In other words, it will create, or build, a standard arch package right then and there, on your system. That's why the text file is referred to both as "Build Files" or as Pkgbuild.
If you look at your screenshot, you see, that it first downloads your PKGBUILD and then shows the file as present (it uses the plural, because in exceptions there are additional files such as systemd-files that are downloaded as well).
When installing apps from the AUR yay will cache stuff to speed up build times. Performing a clean build means not using this cache. In most cases just pressing enter will work just fine.
And now is the part were I must warn you: Be careful with the AUR:
In conclusion. If possible stick with the repos and flatpak. If an app is not available this way you can use the AUR. If you use the AUR you can keep just pressing Enter until the app in question is installed. Just don't be surprised if the app breaks two months later because of something stupid the Manjaro devs did
Cleanbuild means not to use previous existing files, the numbers are exemples of a selection of which packages to cleanbuild. ^4 means all but number 4, the others I think are self explantory
Im not here to explain it because other people already did but imma point out that manjaro is meant to be beginner friendly and the aur isnt so i wouldnt use it in your place.
I wouldn't use manjaro either /s
Jokes aside, everyone's a beginner at some point and you only learn by exploring things that you aren't familiar with
Yeah manjaro is really good for beginners to learn pacman but i would try to install arch first(as its pretty easy bur it teaches you partitions and boot stuff) and then try the aur.
I would guess that "Build Files Exist" means makepkg successfully downloaded the files it needs to build the package. I assume cleanBuild is referring to the building of packages itself.
As for the options, my guesses are:
N
don't install anything and continueA
build and install all the listed packagesAb
interrupt everything and exitI
rebuild packages which are already installed, but don't install new onesNo
build and install packages which are not installed on the systemI think you can also pick specific packages by referring to their index
1 2 3
)1-3
)^4
)Note that I don't use arch btw so I'm only guessing.
[N] builds normally.
[A] deletes the source code from your machine and starts building from scratch.
[Ab] aborts like you'd expect.
[I] clean builds only installed packages.
[No] Idem, but only not installed packages.
He is not a very experienced Linux user and needs help understanding the messages you see in the screenshot. There are about 40 different clues to suggest this in his post, including the fact that he posted the question in the first place—but apparently you missed all of them. How embarrassing for you.
This is a perfectly civil question that is intended to make the author think about what they're reading in the future, rather than spoon feed pure information
You know, that's kind of the point. Either way any repository is technically an user repository that can be added to apt.