PKGBUILD class (points covered) Note: CalimeroTeknik‘s notes for the end of the class are at the bottom ------------------------------- Location: irc.freenode.net #archlinux-classroom Date: Saturday, April 19ᵗʰ 2014 * 9:30AM UTC (~7:30PM in Australia) — class is over, log is here http://sprunge.us/bbcK * 4PM UTC (~10AM in the US) Vote with '1's on the 'votes:' lines under the points you want to hear about! We'll spend more time on those with a lot of votes. 1. Introduction to packaging 1.1 - Q & A: Arch Linux packages and their format. votes: 0 1.2 - Arch packages' metadata, an overview. votes: 2 1.3 - So how do we make them? PKGBUILDs and what they mean. votes: 0 Q & A 2. How PKGBUILDs work 2.1 - Let's build a package! Practical prerequisites. votes: 0 2.2 - Everybody builds an example package! votes: 0 Q & A 2.3 - The PKGBUILD and its essential parts. votes: 1 Q & A a 10mn pause for our brains! tea time and cat pictures allowed~ votes: 4 3. Writing PKGBUILDs 3.1 - It's written in Bash: caveats, robustness. votes: 1 3.2 - How to (correctly) write the functions to compile the package. votes: 1 Q & A 3.3 - Special PKGBUILDs: development packages using GIT and Subversion. votes: 4 Q & A 3.4 - Split packages? votes: 2 More discussion The class itself is kind of over, but you're probably still curious, or have weird questions about packaging. Now's the time! * About the guy hosting the class: I'm a French student and an Arch Linux user since 2008. I notably like C, bash, 日本語, and stuff that is neatly done. My little Arch Linux liveCD is http://ctkarch.org ==== class start ==== 2014-04-19 15:58 eveybody: you can vote under the items you're interested in, here: https://pad.riseup.net/p/pkgbuild-class-apr2014 *** edit:5 votes and points covered are above 2014-04-19 15:58 Title: Riseup Pad (at pad.riseup.net) 2014-04-19 15:58 everybody* 2014-04-19 15:58 yeah, here in IRC 2014-04-19 15:58 ok :) 2014-04-19 15:58 so we can discuss everything as needed 2014-04-19 15:59 how long is ETT? 2014-04-19 15:59 * vorbote (~vorbote@unaffiliated/vorbote) has joined 2014-04-19 15:59 Estimated Time of Termination 2014-04-19 15:59 the previous course was 3608seconds 2014-04-19 15:59 The time it takes to terminate will be 0 2014-04-19 15:59 Earnestly: o/ 2014-04-19 15:59 what was the previous course? 2014-04-19 15:59 same thing 2014-04-19 16:00 9 UTC this "morning" (really this morning in Europe) 2014-04-19 16:00 window merge 2014-04-19 16:00 ugh fail 2014-04-19 16:00 Sat 2014-04-19 16:00 UTC 2014 2014-04-19 16:00 gnubeest: so close 2014-04-19 16:00 * disharmonic (~disharmon@unaffiliated/disharmonic) has joined 2014-04-19 16:01 Sat 2014-04-19 11:01 EST 2014 2014-04-19 16:01 * Fl18 (~Jean@lec67-1-81-56-33-69.fbx.proxad.net) has joined 2014-04-19 16:01 ok my vim is prepared 2014-04-19 16:01 i have sharpened my vim 2014-04-19 16:01 I have made my vim 2014-04-19 16:01 Let's start! 2014-04-19 16:01 i have my vim 2014-04-19 16:02 PKGBUILDs are specification files for building Arch Linux packages, you probably know that since you're here! 2014-04-19 16:02 * hexhaxtron (~onward@cpc7-hari11-2-0-cust916.20-2.cable.virginm.net) has joined 2014-04-19 16:02 the utility 'makepkg' is used to produce a package, feeding it a PKGBUILD. 2014-04-19 16:02 * interpeix (~interpeix@unaffiliated/interpeix) has joined 2014-04-19 16:02 * ovrflw0x (~ovrflw0x@unaffiliated/ovrflw0x) has joined 2014-04-19 16:03 hello, newcomers! 2014-04-19 16:03 so to begin with, the PKGBUILD is written by a maintainer, that's where everything starts 2014-04-19 16:03 * piefge (~none@ip-2-206-0-93.web.vodafone.de) has joined 2014-04-19 16:04 so, we run makepkg, which makes a .pkg.tar.gz file from the PKGBUILD 2014-04-19 16:04 and that package is put in an online repository (generally), then installed with pacman 2014-04-19 16:04 the points I offered to cover during this class are listed here: https://pad.riseup.net/p/pkgbuild-class-apr2014 2014-04-19 16:04 Title: Riseup Pad (at pad.riseup.net) 2014-04-19 16:05 not many votes for the first point, Arch Linux packages and their format 2014-04-19 16:05 I think I'll cover it very fast? 2014-04-19 16:05 right 2014-04-19 16:05 my browser setup is a bit broken, Teach :( 2014-04-19 16:05 concise rundown would be useful 2014-04-19 16:05 let's see what's in a classical package file: you can run `tar tvf /var/cache/pacman/pkg/less-458-1-x86_64.pkg.tar.xz` 2014-04-19 16:06 * dopeamine (~dopeamine@123.237.77.152) has joined 2014-04-19 16:06 so we can see several things in there: 2014-04-19 16:06 all files that must be extracted to / to install the package 2014-04-19 16:06 .PKGINFO, .MTREE 2014-04-19 16:06 * Fl18 has quit (Quit: Lost terminal) 2014-04-19 16:06 * vorbote says please mention .AURINFO 2014-04-19 16:07 …right, that's a novelty but why not 2014-04-19 16:07 .PKGINFO contains name, version, url, dependencies… of the package 2014-04-19 16:07 * Arch-TK says please slow down a tad. 2014-04-19 16:07 * skydrome (~skydrome@unaffiliated/skydrome) has joined 2014-04-19 16:07 * Arch-TK says I kind of unpacked the thing into my home directory. 2014-04-19 16:07 .MTREE (since May 2012) contains info to check file integrity and attributes 2014-04-19 16:08 CalimeroTeknik, should we get the less PKGBUILD from ABS? 2014-04-19 16:08 my command doesn't extract it, Arch-TK :) 2014-04-19 16:08 only lists binary one 2014-04-19 16:08 CalimeroTeknik: well... I extracted anyway 2014-04-19 16:08 hexhaxtron: it's in your /var/cache 2014-04-19 16:08 it's coming, hexhaxtron 2014-04-19 16:08 hexhaxtron: if you didn't clean it 2014-04-19 16:09 so here we have our package 2014-04-19 16:09 now when it's installed : 2014-04-19 16:09 ls /var/lib/pacman/local/less-458-1/ 2014-04-19 16:10 you can see that we can find desc, which contains the info of the package (name, version, dependencies…), it was the .PKGINFO 2014-04-19 16:10 * captainkraft (~captainkr@108.167.46.73) has left ("Leaving") 2014-04-19 16:10 files contains the list of files extracted by pacman (you saw them in the archive) 2014-04-19 16:10 mtree is the .MTREE 2014-04-19 16:11 let's look at a package with an install script: ls /var/lib/pacman/local/filesystem-2013.05-2/ 2014-04-19 16:11 .INSTALL in the archive becomes install in /var/lib/pacman/local/package-version-revision/ 2014-04-19 16:11 I hope you discovered new things here :) 2014-04-19 16:11 really how packages with pacman are made 2014-04-19 16:12 now on to PKGBUILDs! 2014-04-19 16:12 so you could extract the sources by hand, run `make`, run `make DESTDIR='some_dir' install` to put the files in a directory 2014-04-19 16:12 add a '.PKGINFO' file in this folder 2014-04-19 16:12 compress this to an archve (tar cJf "mypackage-0.42-1-$(uname -m).pkg.tar.xz" some_dir) 2014-04-19 16:13 but then when a new version of the software is released, you'll need to do that again… so you'd write a script, right? 2014-04-19 16:13 well, we have even better: PKGBUILDs and makepkg 2014-04-19 16:13 that's it for proving how much it's useful :) 2014-04-19 16:13 * VoidAtValhalla does yaaaay 2014-04-19 16:14 2/ How PKGBUILDs work! 2014-04-19 16:14 (2 of 3) 2014-04-19 16:14 everybody okay so far? 2014-04-19 16:14 * gnubeest claps 2014-04-19 16:14 yep 2014-04-19 16:14 yup 2014-04-19 16:15 instant vote: are you interested in building a package for the sake of it? so you really had something to look at while explaining 2014-04-19 16:15 sure 2014-04-19 16:15 yesh, was expecting to 2014-04-19 16:15 we can go to https://www.archlinux.org/packages/ and find 'less', click on "source files" (top right) 2014-04-19 16:15 I am catching up in the backlog 2014-04-19 16:15 scrollback whatever 2014-04-19 16:16 * VoidAtValhalla uses ABS 2014-04-19 16:16 * tb01110100 (~thomas@unaffiliated/tb01110100) has joined 2014-04-19 16:16 The package system of Arch Linux is called 'ABS', for Arch Build System actually 2014-04-19 16:16 https://wiki.archlinux.org/index.php/Arch_Build_System 2014-04-19 16:16 Title: Arch Build System - ArchWiki (at wiki.archlinux.org) 2014-04-19 16:16 the official ABS tree is the set of PKGBUILDs maintained by the arch developers. 2014-04-19 16:16 * tb01110100 rushes into the classroom and sits down, hoping no one will notice 2014-04-19 16:16 and of course, in AUR, anybody can post their PKGBUILDs. 2014-04-19 16:17 I have a particular package I want to package. It's scrypt 2014-04-19 16:17 nuun: later 2014-04-19 16:17 welcome, here's the backlog tb01110100: http://sprunge.us/JSeR 2014-04-19 16:17 CalimeroTeknik: ty 2014-04-19 16:18 everybody found the PKGBUILD for 'less'? 2014-04-19 16:18 you should be here: https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/less 2014-04-19 16:18 Title: svntogit/packages.git - Git clone of the 'packages' repository (at projects.archlinux.org) 2014-04-19 16:18 yup 2014-04-19 16:18 yes 2014-04-19 16:18 yes 2014-04-19 16:18 yes 2014-04-19 16:18 OK! get that PKGBUILD (click plain), save it to an empty directory (/tmp/foo for instance) 2014-04-19 16:19 and run makepkg with your terminal in that directory 2014-04-19 16:19 if all goes well… tadaa! you just built 'less' from core. 2014-04-19 16:19 oh, wait 2014-04-19 16:19 I forgot, building packages expects you to have installed 'base-devel' 2014-04-19 16:20 PKGBUILDs implicitly expect all packages from the group base-devel to be installed (pacman -Sg base-devel for the list) 2014-04-19 16:20 if you don't, the build will generally fail on things like 'make: command not found' 2014-04-19 16:21 base-devel contains notably: GCC, make, patch, autotools… the basics of what's needed to compile free software projects, generally 2014-04-19 16:21 I hope the build worked for everybody now? 2014-04-19 16:22 yes 2014-04-19 16:22 yup 2014-04-19 16:22 aha 2014-04-19 16:22 yes 2014-04-19 16:22 yes 2014-04-19 16:22 5 people is everybody now apparently 2014-04-19 16:23 ^ 2014-04-19 16:23 that should do it :p 2014-04-19 16:23 nice! to see how that worked, let's get back to the PKGBUILD: https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/less 2014-04-19 16:23 Title: svntogit/packages.git - Git clone of the 'packages' repository (at projects.archlinux.org) 2014-04-19 16:23 first, metadata 2014-04-19 16:23 CalimeroTeknik: I had a warning about sig match but I assume since I haven't -Sy in a couple days? 2014-04-19 16:23 -Syu, you mean 2014-04-19 16:23 Can't we just vim the PKGBUILD we wget-ed 2014-04-19 16:23 -Sy is a bad idea, you could install new dependencies and break the packages you don't update 2014-04-19 16:23 Arch-TK, works as well. 2014-04-19 16:23 Arch-TK: you can use ABS 2014-04-19 16:23 better* 2014-04-19 16:24 VoidAtValhalla, abs is generally out of date 2014-04-19 16:24 the svn repo is what the developers use 2014-04-19 16:24 Which repo? 2014-04-19 16:24 everybody: this "ABS" is a copy of the development repositories containing the PKGBUILDs for all official packages 2014-04-19 16:25 this repo: https://www.archlinux.org/svn/ 2014-04-19 16:25 wow never experienced anything older in ABS than in repo, thanks for info :) 2014-04-19 16:25 * fsckd uses a git mirror git://projects.archlinux.org/svntogit/packages.git 2014-04-19 16:25 so I could use ABS instead of going for the git clone? 2014-04-19 16:25 I * 2014-04-19 16:25 oops 2014-04-19 16:25 I always have that problem, VoidAtValhalla 2014-04-19 16:25 noted :) 2014-04-19 16:25 ABS is misleading, I think I need to make this clear 2014-04-19 16:25 oh 2014-04-19 16:25 ABS means Arch Build System 2014-04-19 16:26 it is the techniques and tools used to build packages for Arch Linux 2014-04-19 16:26 * Topic for #archlinux-classroom is: Next PKGBUILD Class will be on 19th April 2014 @ UTC 9 AM and UTC 4 PM | The prior PKGBUILDS class was Sept 14, 2013. Class log is at https://archwomen.org/media/project_classroom/classlogs/2013-09-14-beginner_pkgbuilds1.txt 2014-04-19 16:26 * Topic for #archlinux-classroom set by tigrmesh!~tigrmesh@archlinux/op/tigrmesh (Wed Apr 16 03:21 2014) 2014-04-19 16:26 Not "Anti-lock braking system" 2014-04-19 16:26 Ok. 2014-04-19 16:26 noted 2014-04-19 16:26 For a second there, I thought my operating system was a car. 2014-04-19 16:26 Arch doesn't need brakes :P 2014-04-19 16:26 hehe 2014-04-19 16:26 but the "ABS" VoidAtValhalla was speaking about is a server that has a copy of the PKGBUILDs from the official repositories 2014-04-19 16:26 >chanserv< op #archlinux-classroom tigrmesh 2014-04-19 16:26 * ChanServ gives channel operator status to tigrmesh 2014-04-19 16:26 are we clear now? 2014-04-19 16:27 Yes 2014-04-19 16:27 I think so. 2014-04-19 16:27 since "ABS" has become the name of the repositories with all the official PKGBUILDs, these: https://www.archlinux.org/svn/ 2014-04-19 16:27 sorry for misleading anyone 2014-04-19 16:27 also the ones we were looking at the PKGBUILD for 'less' from 2014-04-19 16:27 no, you gave an opportunity to explain this :) 2014-04-19 16:27 so! that PKGBUILD 2014-04-19 16:28 you can see from line 5 to 16, metadata 2014-04-19 16:28 the name of the package of course 2014-04-19 16:28 * tigrmesh has changed the topic to: PKGBUILD Class happening right now. Points being covered are here: https://pad.riseup.net/p/pkgbuild-class-apr2014 2014-04-19 16:28 (it's limited to a-z and _ and -) 2014-04-19 16:28 >chanserv< deop #archlinux-classroom tigrmesh 2014-04-19 16:28 * ChanServ removes channel operator status from tigrmesh 2014-04-19 16:28 then you have pkgver 2014-04-19 16:29 be careful; it's the version of the software you're packaging 2014-04-19 16:29 pkgrel is the release of your package: if you update your package but the sources are the same, change pkgrel 2014-04-19 16:29 if new sources are released upstream, change pkgver and put pkgrel back to 1 2014-04-19 16:29 that's important, so people understand that it's just a necessary rebuild, but the software is the same version 2014-04-19 16:30 (or you fixed your PKGBUILD) 2014-04-19 16:30 pkgdesc is self-explanatory. 2014-04-19 16:30 arch is the hardware architectures the package is known to run on 2014-04-19 16:30 * dopeamine has quit (Ping timeout: 240 seconds) 2014-04-19 16:30 if it's just a script, you should put arch=('any') in there: the package doesn't need to be rebuilt to run on another type of processor 2014-04-19 16:31 Emphasis on KNOWN (It doesn't mean expected) 2014-04-19 16:31 CalimeroTeknik: are maintainers required to do tests on source code like malware scan before they posting it in AUR? 2014-04-19 16:31 i686 or/and x86_64 or any 2014-04-19 16:31 and arm 2014-04-19 16:31 right 2014-04-19 16:31 you can put arm in there if it worked 2014-04-19 16:31 even mips… I don't know 2014-04-19 16:31 url is the url of the project's site 2014-04-19 16:32 sometimes there is no site, it's a bit tricky… it might be a forum thread 2014-04-19 16:32 groups is interesting. groups in Arch packages don't really "exist" 2014-04-19 16:32 there is no list of packages for a group 2014-04-19 16:32 please use correct url guys ... even official packages are sometime broken by wrong url 2014-04-19 16:32 well, it breaks nothing 2014-04-19 16:32 it's only informative 2014-04-19 16:33 we'll come to source=() in a few seconds 2014-04-19 16:33 but before that, groups. 2014-04-19 16:33 a package claims to belong to a group 2014-04-19 16:33 that's how groups work 2014-04-19 16:33 there's nothing more to it 2014-04-19 16:33 when you ask pacman to install a group, pacman -S group 2014-04-19 16:34 CalimeroTeknik: sure it will work but i consider it broken when you wan to look at upstream and all you get is wrong url :) 2014-04-19 16:34 indeed. 2014-04-19 16:34 so when you pacman -S group, pacman just installs the packages it knows of in its remote DBs, that claim to belong to the group. 2014-04-19 16:34 depends: it's the dependencies the package needs to run 2014-04-19 16:35 we also have makedepends: they are needed when running makepkg 2014-04-19 16:35 and only then 2014-04-19 16:35 optdepends are dependencies you may want to install, but that the package can run without (some features might not be available) 2014-04-19 16:35 okay, now, source! 2014-04-19 16:35 and base-devel is a given for make depends. No need to call it? 2014-04-19 16:36 indeed, it's implicitly required if you want to build packages 2014-04-19 16:36 that's in the guidelines 2014-04-19 16:36 ok 2014-04-19 16:36 by the way, everything on packaging is here: https://wiki.archlinux.org/index.php/Category:Package_development 2014-04-19 16:36 Title: Category:Package development - ArchWiki (at wiki.archlinux.org) 2014-04-19 16:37 take note of this link for future reference if you intend to make PKGBUILDs, and even more if you intend to share them 2014-04-19 16:37 I won't post many links in this class, so it be only really relevant info 2014-04-19 16:37 * benjamin1 (~benjamin@ppp-88-217-108-149.dynamic.mnet-online.de) has joined 2014-04-19 16:38 so far so good, ma'am 2014-04-19 16:38 so, source=( … ) in the PKGBUILD: it's an array 2014-04-19 16:38 for instance, source=('http://something' 'http://something-else') 2014-04-19 16:39 that downloads what these two URLs point, and will extract them for you before running the build() function. 2014-04-19 16:39 makepkg will do that for you 2014-04-19 16:39 this seems unenforceable, which is why all of us should carefully review any PKGBUILDs from AUR before we install the the package. CalimeroTeknik: are maintainers required to do tests on source code like malware scan before they posting it in AUR? 2014-04-19 16:39 sorry for the interruption 2014-04-19 16:39 tigrmesh: thanks 2014-04-19 16:39 true! 2014-04-19 16:40 * Ploppz (~ploppz@ti0276a430-1385.bb.online.no) has joined 2014-04-19 16:40 * toonces has quit (Disconnected by services) 2014-04-19 16:40 oh, I'm sorry for dropping your question 2014-04-19 16:40 * benjamin1 is now known as toonces 2014-04-19 16:40 no problemo ;) 2014-04-19 16:40 Oh, too late for the class :SS Is it long time since you started? Can I get a log? 2014-04-19 16:40 Yes 2014-04-19 16:40 * toonces (~benjamin@ppp-88-217-108-149.dynamic.mnet-online.de) has left 2014-04-19 16:41 I am also busy right now so where do I find a log afterwards? 2014-04-19 16:41 http://sprunge.us/CDfP - A crude log 2014-04-19 16:41 It started at 17:00 2014-04-19 16:41 Okay, thanks 2014-04-19 16:41 16UTC 2014-04-19 16:41 9PST 2014-04-19 16:41 Yes, but this was the time for the log. 2014-04-19 16:41 oh, right 2014-04-19 16:42 Ploppz, it will be at https://archwomen.org/media/project_classroom/classlogs/ 2014-04-19 16:42 Title: Index of /media/project_classroom/classlogs/ (at archwomen.org) 2014-04-19 16:42 >chanserv< op #archlinux-classroom tigrmesh 2014-04-19 16:42 * ChanServ gives channel operator status to tigrmesh 2014-04-19 16:42 so, after that we have md5sums: it's checksums for the files 2014-04-19 16:42 it's so you really get the file the maintainer tested 2014-04-19 16:42 Thanks 2014-04-19 16:42 of course SKIP is allowed 2014-04-19 16:42 is it md5sums by default? 2014-04-19 16:42 * sr (~smrgr@shellium/member/samruger) has joined 2014-04-19 16:42 * tigrmesh has changed the topic to: PKGBUILD Class happening right now. Points being covered are here: https://pad.riseup.net/p/pkgbuild-class-apr2014 class log will be at https://archwomen.org/media/project_classroom/classlogs/ 2014-04-19 16:43 we used md5sums from the start, but now, sha256sums are supported 2014-04-19 16:43 you can include both if you want, or any of the two 2014-04-19 16:43 nuun: it doesnt matter if md5 or sha it just need correct variable name 2014-04-19 16:43 you can write sha256sums=('dc51b8c96c2d745df3bd5590d990230a482fd247123599548e0632fdbf97fc22') etc 2014-04-19 16:44 any tricks for the maintainer to check that the sources are correct when originally downloading and making the hash? 2014-04-19 16:44 (It's also an array, which corresponds to the files, imagine it as zip from python) 2014-04-19 16:44 tigrmesh, I'm afraid there's none, do you have any? 2014-04-19 16:44 no 2014-04-19 16:44 I use makepkg -g 2014-04-19 16:44 but this is not really a security class 2014-04-19 16:44 true. as you were ;) 2014-04-19 16:45 makepkg -g allows you to generate the checksums, nuun, indeed 2014-04-19 16:45 you can then add that to the PKGBUILD so other people can have makepkg check that before building 2014-04-19 16:45 nuun: The question was related to checking the actual validity of the files used to make the package, not generating md5 hashes. 2014-04-19 16:45 I'm afraid we'd need a trust chain for that 2014-04-19 16:46 with GPG keys or something 2014-04-19 16:46 Yes. 2014-04-19 16:46 That's the obvious answer. 2014-04-19 16:46 Continue. 2014-04-19 16:46 before the pause, we're going to gloss over the build() and package() functions in the PKGBUILD for 'less'. 2014-04-19 16:47 package() is really the only function you absolutely need to include in a PKGBUILD 2014-04-19 16:47 oh, wait. when these functions are run, variables are defined. 2014-04-19 16:47 "$srcdir" where makepkg extracted the sources that were in sources=() 2014-04-19 16:47 it's the path to that directory 2014-04-19 16:47 and, "$pkgdir" which is an empty dir created by makepkg so you put the files to be compressed into a package in there 2014-04-19 16:48 * Arch-TK hopes you talk about the version function in the github package making section. 2014-04-19 16:48 you can see lots of references to these variables in those functions 2014-04-19 16:48 sorry, what? 2014-04-19 16:48 I'm still on https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/less 2014-04-19 16:48 Title: svntogit/packages.git - Git clone of the 'packages' repository (at projects.archlinux.org) 2014-04-19 16:48 Yes, that's fine. 2014-04-19 16:48 Don't worry. 2014-04-19 16:48 I'll ask again in Q&A if you don't mention it in the end. 2014-04-19 16:49 oh, sorry, yes. it's in VCS PKGBUILDs 2014-04-19 16:49 it's not github, it's git 2014-04-19 16:49 github is a company! 2014-04-19 16:49 so, the package() function is where you write the commands you need to run to put files into your package. 2014-04-19 16:50 it should do *only that* 2014-04-19 16:50 it can take stuff from the sources that are in "$srcdir", and put them in "$pkgdir" to achieve its goals 2014-04-19 16:50 what do you mean? what else would it do? 2014-04-19 16:50 then, the build() function is where you put commands that actually construct binaries 2014-04-19 16:51 i'll wait. sorry 2014-04-19 16:51 anything that relates to compiling the sources is in there 2014-04-19 16:51 you were just on time tigrmesh :) 2014-04-19 16:51 additionnally, we have prepare() which is not in this PKGBUILD, if you need to apply patches to the sources before compiling them 2014-04-19 16:52 that way, the patches will be only applied once even if you run makepkg several times 2014-04-19 16:52 we're done with this! pause! 2014-04-19 16:52 omg is it cat picture time 2014-04-19 16:52 yup 2014-04-19 16:52 * gnubeest claps 2014-04-19 16:52 * VoidAtValhalla claps too 2014-04-19 16:52 the next part will actually start with lots of lulz as well :) 2014-04-19 16:52 * nuun appends applause 2014-04-19 16:53 the boring part is over, that is 2014-04-19 16:53 Right... I'm going to find something to drink. 2014-04-19 16:53 i protest! today is Saturdog 2014-04-19 16:53 I am going to fix up a browser ... 2014-04-19 16:53 I'm already making improvements to my old PKGBUILDs 2014-04-19 16:53 CalimeroTeknik: this is awesome, thank you for doing this, it forces me to do something i never got around to doing myself 2014-04-19 16:54 next part is… Writing PKGBUILDs… and I'll start with how not to do it 2014-04-19 16:54 gnubeest: I think I am sexist ... I have been taught mostly by women my whole life. 2014-04-19 16:54 nuun: i think you are sexist for even mentioning that. 2014-04-19 16:54 http://i.imgur.com/prvOkD3.gif 2014-04-19 16:55 gnubeest: I have had only 10 male teachers in 5 institutions 2014-04-19 16:55 no to step on CalimeroTeknik's toes, but i think the 2 of you are veering offtopic 2014-04-19 16:55 Hmm... 2014-04-19 16:55 About half my teachers are male. 2014-04-19 16:55 oop. make that 3 2014-04-19 16:55 it's pause time tigrmesh :) 2014-04-19 16:55 ohhh 2014-04-19 16:55 how often do these classes take place? 2014-04-19 16:55 tigrmesh: It's #archlinux-offtopic time 2014-04-19 16:55 that's also why I've stopped flooding 2014-04-19 16:55 bring on the bunny videos 2014-04-19 16:56 you got it 2014-04-19 16:56 sr, not often. sorry 2014-04-19 16:56 https://i.imgur.com/fo1LTb0.gif 2014-04-19 16:56 http://placekitten.com/ 2014-04-19 16:56 Title: {placekitten} (at placekitten.com) 2014-04-19 16:56 This PKGBUILD is horrible... What the hell did I drink before writing this? 2014-04-19 16:57 Arch-TK, you're already starting the next point of the class :p 2014-04-19 16:57 so you noticed it, eh? :p 2014-04-19 16:57 No, this is an old PKGBUILD I wrote for easy instalation of FBGL 2014-04-19 16:58 Which is also my own crappy project 2014-04-19 16:58 oh, right. I was talking about the PKGBUILD for 'less' 2014-04-19 16:58 It's a terrible mess. It's soon going to be superseeded by FOXI (FBGL on Xlib Instead) 2014-04-19 16:58 So I can write a more sensible makefile for it. 2014-04-19 16:59 Or even better, a configuration script. 2014-04-19 16:59 makefile .... 2014-04-19 16:59 * disharmonic has quit (Quit: Leaving) 2014-04-19 16:59 CalimeroTeknik: no automagic way to create PKGBUILD, or is it alway created manually? 2014-04-19 16:59 * VoidAtValhalla 's head explodes 2014-04-19 16:59 Hey! My makefiles are world class impossible to understand. 2014-04-19 16:59 CalimeroTeknik: I came across https://dudle.inf.tu-dresden.de/ 2014-04-19 16:59 Title: dudle (at dudle.inf.tu-dresden.de) 2014-04-19 17:00 is it useful to you? 2014-04-19 17:00 gnubien, you can start off from another PKGBUILD but yeah, you write it by hand 2014-04-19 17:00 nuun: what is it ? 2014-04-19 17:00 you can copy-paste a PKGBUILD that's alike, that is 2014-04-19 17:00 CalimeroTeknik: right, use a template 2014-04-19 17:00 there is no good template available even on the wiki, though 2014-04-19 17:01 for reasons I'm going to talk about right now 2014-04-19 17:01 ok, thanks 2014-04-19 17:01 after this course, you'll be better at making PKGBUILDs than the Arch developers themselves, that is 2014-04-19 17:01 …some of them at least 2014-04-19 17:01 pause ends in a few seconds! 2014-04-19 17:01 time for lulz 2014-04-19 17:02 * gnubeest claps 2014-04-19 17:02 * nuun steams away the low self-esteem 2014-04-19 17:02 CalimeroTeknik,nuun: why not just use doodle.com ? 2014-04-19 17:02 why for? 2014-04-19 17:02 plan a meeting? 2014-04-19 17:02 VoidAtValhalla: KISS is great 2014-04-19 17:02 we all meet here 2014-04-19 17:02 yup 2014-04-19 17:03 voting and also for plan when classroom will be next time :) 2014-04-19 17:03 ok, sure 2014-04-19 17:03 easier for me to tmux from another box too 2014-04-19 17:03 ~ pause ends ~ 2014-04-19 17:03 * VoidAtValhalla stops playing with mobile 2014-04-19 17:03 so I didn't dwell on it too much earlier… but PKGBUILDs are in Bash, right? 2014-04-19 17:03 the shell you use every day, right? 2014-04-19 17:03 well, that or zsh 2014-04-19 17:04 let's try a fun experiment 2014-04-19 17:04 you built 'less' in /tmp/foo, for instance 2014-04-19 17:04 * VoidAtValhalla waits for explosion 2014-04-19 17:04 try to rename that folder to 'build folder' 2014-04-19 17:04 and run makepkg again 2014-04-19 17:05 you can run makepkg -f or remove the package that was already built, of course 2014-04-19 17:05 can someone paste the error that happens? :p 2014-04-19 17:06 * gnubeest builds it quickly because he was cooking the first time 2014-04-19 17:06 note to build the package in a folder called "test folder" 2014-04-19 17:06 or something with a space in its name 2014-04-19 17:06 * CalimeroTeknik waits for it, giggling 2014-04-19 17:07 ==> Starting build()... 2014-04-19 17:07 /home/kyle/builds/test folder/PKGBUILD: line 19: cd: /home/kyle/builds/test: No such file or directory 2014-04-19 17:07 exactly 2014-04-19 17:07 what happened? 2014-04-19 17:07 cd ${srcdir}/${pkgname}-${pkgver} 2014-04-19 17:08 this expanded to `cd /home/kyle/builds/test folder/less-458` 2014-04-19 17:08 and so, /home/kyle/builds/test is non-existent 2014-04-19 17:08 the correct answer is: cd "${srcdir}/${pkgname}-${pkgver}" 2014-04-19 17:08 Wait, you want me to rename it to build space folder? 2014-04-19 17:09 Arch-TK, whatever, so long as there's a blank character in the name of the directory that contains the PKGBUILD 2014-04-19 17:09 Ok. 2014-04-19 17:09 then you run makepkg… and KlipKyle posted the result 2014-04-19 17:10 Yeah... 2014-04-19 17:10 so, it is spaced package names are possible? 2014-04-19 17:10 the PKGBUILD is not robust line 19, cd ${srcdir}/${pkgname}-${pkgver} 2014-04-19 17:10 this must be quoted 2014-04-19 17:10 /tmp/build folder/PKGBUILD: line 19: cd: /tmp/build: No such file or directory 2014-04-19 17:10 nuun, no, no, the folder doesn't matter 2014-04-19 17:10 Yes, because someone didn't use "" around everything. 2014-04-19 17:10 the directory* 2014-04-19 17:10 So we fix the MAKEPKG then? 2014-04-19 17:10 I mean... 2014-04-19 17:10 no, the PKGBUILD 2014-04-19 17:10 PKGBUILD 2014-04-19 17:11 That's the one. 2014-04-19 17:11 it's just that one must be very wary to quote properly the character strings in Bash, and so, in PKGBUILDs > nuun 2014-04-19 17:11 The pacman PKGBUILD itself was missing quotes: https://bugs.archlinux.org/task/38368 2014-04-19 17:11 Title: FS#38368 : [pacman] PKGBUILD has unquoted strings (patch) (at bugs.archlinux.org) 2014-04-19 17:11 so I reported that, it was too ridiculous 2014-04-19 17:11 thanks 2014-04-19 17:11 and here are the lulz we were all waiting for… 2014-04-19 17:11 One fateful day, the author of bumblebee forgot to quote a string in his install script, you surely know about it. 2014-04-19 17:12 woe ensued: https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/commit/a047be85247755cdbe0acce6f1dafc8beb84f2ac 2014-04-19 17:12 Title: GIANT BUG... causing /usr to be deleted... so sorry.... issue #123, issu... • a047be8 • MrMEEE/bumblebee-Old-and-abbandoned • GitHub (at github.com) 2014-04-19 17:12 lol was wondering if this would be mentioned 2014-04-19 17:12 so *QUOTE YOUR STRINGS* 2014-04-19 17:12 really. 2014-04-19 17:12 write better PKGBUILDs than the Arch developers do. 2014-04-19 17:12 That's actually... really funny. 2014-04-19 17:12 please, do it for /usr, do it for the kittens 2014-04-19 17:13 http://www.kirikoo.net/images/14Anonyme-20140419-093203.png 2014-04-19 17:13 Well, one could make makepkg set a more sane IFS ;p 2014-04-19 17:13 let's see 2014-04-19 17:13 nope. 2014-04-19 17:13 hm? 2014-04-19 17:13 that's not going to solve anything 2014-04-19 17:13 It is 2014-04-19 17:14 it's the word splitting that breaks it 2014-04-19 17:14 If it was zsh it would work 2014-04-19 17:14