The most common/familiar one is probably using a makefile. Usually a git project will provide instructions on the project page. this is general linux, or project-specific. sometimes that isnt feasible due to time or knowledge, etc.Īnd in this case you probably wont be seeing much in the way of updates or conflicts (guessing anyways). even when we must go outside our normal repos, and even beyond the AUR, we would technically prefer to create a PKGBUILD to have an ALPM (arch package) compatible install file and all the niceties listed above - it also means it can be shared with others to easily use the same software.īut. The main thing here is that you would probably prefer to have a package that the package manager recognizes - so it can be easily updated, removed, and the system files are also tracked by the package manager - helping with things like conflicts and dependencies. Will work on your mac, i too old macbookpro 2006. The display audio driver support windows 8. 20 question, q, no sound on 27 inch imac mid 2011 running windows 8.1 on botcamp. I wont get into transparency, trust, third party repos, and all that. I just installed 8.1 on my mac and everything went very well. but that is generally the scale from most to least preferred.
4 ) Manual build/install (outside of package managers).Lets do a quick (rough) breakdown of preferred install methods of software. but we have to cover some interdependent basics.
