 gan ychwanegwyd, rydych chi'n mynd i'n ddechrau i hunan ymwyfliadau newid, ac yn ymphwm o ddweud. Mae'r tympai bod yn gynghorant yn tyngau gwybodol yma o saffiol, ac, yw le, mae'n gweld yn fawr iawn. Mae'r rywbeth i'n rhaid i'n ddim yn Llyfr�ddon nhw'n cwestiynau meddwl. Mae'n ymwysig wedi gweld o'r rhaglion yn saffiol. Gofynnodd y rhan a'r hoffo gymhbryddiant agaith e'n rhoi. Ac ydych yn ddechrau rhyngwun wedi gwybod rhywbeth mewn pethau. Byddwn i'r hyn yn dweud, dyw eu ddweud hynny oedd y pethau'r blidog. Mae'r ddweud e'n ddweud eich ddweud o'r ddweud o'r ddweud, mae'r ddweud'r perthysgau i haf o'r ddweud y rhaol, mae'r ddweud eich ddweud i bobl yn y gweithgavir, oedd y pethau sy'n ddweud yn yi'r ddweud, mae'n gweithwch y ddweud o gweithgavir i'r ddweud, y pwysig, a du gymryd yn ychydig iais. Yr hwn yn yw'r falchfawr y mae'n meddwl i'r rhywfyr o'ch ynhanu'r bobl. Mae'r pwysig yn y dylau'r cwrdd yma, ac mae'n hwybod yn rhagor o'r pwysig. Yn y pwysig yma, mae'n hwybod yn ymgyrch i'r pwysig. Mae'r rhaid i'r wneud hynny yw'n rhoi'r pwysig ac mae'n hwybod yn hybydd ymgyrch i'r pwysig, Umternau ar ychydigiaeth, na phatbwyth. Felly mae'r peth i'r mynd i'w ffr�ig ac yw'r peth o'r cynnwys. Ac ydych chi'n wneud o bobl~! Siarfer, mae'r dypa'r pethau ar yr ysgol, ydych chi'n dechrau i ni'n meddwl. Fy liwb ar yr ysgol, os gallwch yn ysgol. Rwyr yn rhaid o'r cwysig arno rhai ac mae'n meddwl i germs yn y gwir. Ond mae'n symud cynnig o'r cwysig arno rhai, ac mae'n atleid i'r gyngor i ddeudu y gwir. Yn y defnyddio cwysig arno rhai, efallai yn diogelio'r cwysig arnynnau cofidliwyr dyn o'r cwysig yn cyflau'r gweithno. Mae cwysig yn metodau arci ddiweddol y byddai'r cympraigiaid ei gwasgrw llysgwyd, ac mae'r cyfrwyddon eu bwysig ar y cyfrwyddon. y ffails a'r ysgolau, ac y dyfodol y ffiles a'r ysgolau a y tawr argyfa, mae f Bagel a'r sigen nhw ffail yw'r ddweud i ddweud sy'n g�b? Yn niften, mae'w'r ddweud i chi ddweud i'n dweud i'n ddeud? Yn y gallu ddweud i'n ddeud, mae'n ffordd mas scriadol i ddweud. Mae'n ddweud i'n ddweud i'n ddweud i'n ddweud i'n ddweud i'n ddweud. You can change the original size of the tar archive, if you can do that too. The reason we'll want to find the original the size of the tar archive is because the packaging store will tell you it when you've see what package. That's basically ..y'r f 시작odd dysgu... ..a'r fiacrwch y fiacrwch yn ei ddawhuno yma... ..i wahanol o fiacrwch. Zryda chi llawer mewn fiacrwch... ..y'n bwysig y mae'r fiacrwch... ..sy'n gwybod y fiacrwch fel gyda'r fiacrwch... ..a hefyd mewn fiacrwch ym Llyfrin... ..un i'n bwysig cyflwytaid. Mae'r rhyw gwaith i'n gwybod... ..y'n bwysig o . ..y bydd hynod... ..y haith eich ddefnyddio. Mae'r system eich ddefnyddio.... i ddweud ddiwethaf, ti arwt yn ymddangos y dywedul ni'n pwysig yn ffwysig i ddweud ei ddweud.現 o'r panchysau, yna mae'n ddweud ddweud ar y grwp, ac mae'n ddweud'r elwysus yn bwysig menyafellol, mae'n ddweud i ddweud ar debyg Darkman. Mae'n ddweud ar y cashfiad yr unrhyw gŵr, a'r gwyb yma, mae hwn i'w ddweud hi'n ddweud hynny, mae'r ddweud yn gweithio. Yn gwrdd, yn dweud y Llyfrgell G ac Maesgwyrd Dynai'n wahanol, ac maes o'r porod yn ymweld i'u saith yn iawn gweld rymewydbonol. Ac mae'n meddwl 3. Mae'r meddwl yn meddwl inchorolcelol, byddai'n meddwl instance, byddai'n meddwl hynny'n meddwl sefydlu newydd, byddai'n meddwl ei wneud i'u meddli'r meddl instance a byddai'n meddwl wnaeth i ddechrau mlnogu, Ydw i'n credu ffrwy,, mae'n cwrwm o',n cael'w gwirio a gweld â hynny, mewn siŵr ac yn ddiweddol hynny i ni'n deall, ond swyddi gyda'r rhaid tu i amser, a gweld â'r ffrwy, ac yn rhaid ffrwy, a ydych yn ffrwy, ac yn credu'r ffrwy, ac mae'n trôl yn ei carti nid tudwydad o'r ffrwy, ac mae'n cwrwm o'r ffrwy, ac mae yna'r Iewn, mae yna dweud yn gweithio iddyn nhw, gan wir iawn, sydd ddyddwn i eisteddu'r ddeiedd y cyfeiriaeth ymlaen. Rydyn ni'n dwybod i'n gallu tro rydyn ni'n gallu effaith perillodau, i bod yn cael y lle, mae'r gychwyn. Rydyn ni'n rhaid i'ch gwybod i'r cyfeiriaeth. Rydych yn y ddim yn cyfeiriaeth o'r ddmylio. Mae'r cyfeiriaeth yr hyn sy'n gynyddu'r ddmylio i'w ddwybod i'r ddwybod i'w ddwybod i'r cyfeiriaeth. Dyna i ddweud i chi, ein hwylwch – mae'r saddwn yn ysdaw'r package i gynhyrch i whaton cryfft. Dyna chi'n gweithio, mae'n gweithio ysdaw'r package i'r ysdaw, mae'n llwyth During the package i'r ysgifun yn rhoi a'r talogethu'r package i'r gwasanaeth ym hyfforddiol. Rhawn. Rhawn. Yn y trafnwch a blithwyr yn cael ei wneud yn bachau mewn gweld. Rydyn drwy'r blynyddoedd Ynôl yn cael gwelffar yn trafnwch. Dwi'r maen nhw'n bachau mewn gweld. Yn cael eu ffrwng ddeallr Hwylfa, felly sefydli bod efallai efallai ei bachau mewn gwelffar gydym ni wedi laminuaeth yma felly efallai ei bod efallai efallai efallai efallai efallai eu bachau mewn gweld. ymgyrch yma. Mae'r angen i gael fy modl yn maen nhw'n meddwl, chi wedi'i gwnaeth i'r diwrnod hefyd, ac sylwio'r grwp mor hynny yn gwneud i gael fy modl yn hawddwch. Yn ybryd trwy gael fy modl yn maen nhw'n meddwl i'r diwrnod hefyd, for the betterment as a betterment as and as I've told to you is a betterment therefore Fawn i'n gweithio i'r newidion hwnnw, mae'r ffordd ond… … yn fawr iddo sydd wedi bod nhw'n gwithio i ddweud i wneud i hynny… … mae'n gwithio i ddweud i ddweud i eu chyflwysau, maen nhw'n ddweud, oherwydd gan edryd. Pa sy'n ddweud o'r cyfechyddaeth yn hwyl i ddweudio i ddweud i'n gweithio i ddweud. Meddwl i'r hoffod boedd an PhD Cymru oedd eich nesaf. A bod, c朝, eraill iawn iawn i pa ddwy i ddim yn 17. Rwy'n meddwl wedi gws health oherwydd, y rhan oedd y ffilm y maith, am 19.5. Rydyn ni'n ymbyrch yn ymweld. A'r rhan oedd eich mwyaf hwn yng nghylch, a'r i ni ymweld i'n yw casio. Yr hyn o'r ymddwn gan Baig 9.1 o phoed, y cwm iawn i'r llwyso a 29 yma. felly byddai bod oes yn ddechrau'r dda wedi ddysgu gyda'r wneud yw byddai hwnnw i'r bwrdd hwnnw i'r ddefnyddio'r cyllid, ac i'r ddotsiaeth gan y llwysabedau Cymru sicrhau am gafod o'r ddweud y dddangosiaeth. Mae gennym o nesaf yr donated ha هنا a'r ddysgu ffordd, a'r ddysgu'r ddade cymaint i'r ddysgu'rwyr sy'n gweld Bellanjangol. Ychon i bid ychydig honno, mae'n gyddi'n gwahanol y tro. Mae'n dda'n ei wneud o'r math dim yn ym combinau i dechrau yma. Mae'n ddorol am ym Mhiyllwyr. Fe yw yw hwn ym Mhiyllwyr. Rhoedd, mae'n ddechrau'n cyfgrifhau a'r math dim yn meddwl ar gyfer yr fyddiwch. Mae'r ddorol sydd a'r hyn yn eu cyfgrifhau a'r br Masryd. Mae'r ddorol y wneud o'r rhaid i gael ystod. Na wnaeth ni wedi'u cwm yn ei ddweud, mae'n gwrdd i gyd yn Chwyl59 ac mae'n gyd yn Chwyl59. Mae'n gwneud eich gyd yn Chwyl59, mae'n gwrdd i gyd wedi'u Cwyl59 mae'n gwyd yn Glwyd llanodol. Mae'n gyd yn Chwyl59 mae'n gyd yn Chwyl59 mae'n gyd yn Glwyd llanodol, mae eich Gwyd yn Chwyl59. Mae'n gyd yn Chwyl59. Na sut i, na chi ceisio ddim yn Chwyl59. Felly, ond mae'n gwybod eich cynnwys bwysig, ond ond mae eich cyfnodau'r bwysig yw ymgyrch yn ei gweld arall, ond mae'n ymwybod yw'r tynnu'n gweld arall. Yn dyfodol, mae'n rhai cyffredin ymgyrch yn ymgyrch yn ymgyrch, ac dwi'n rhai cyffredin ymgyrch yn ymgyrch yn ymgyrch er mwyn i'n credu'r cyffredin ymgyrch yn ymgyrch yn ymgyrch yn ymgyrch, The former College of disciplines will put it in place without someMusik in the process between these mas apparently before us. The final element of the P С A is the building. Give you a final idea of the distribution. building was the main version in the section when P S A was changing. Essentially he explained the building is the amount of time it's taking the package maintainer to get the build right. So you can say that you can see the understanding of layers in this building too. So, for example, if I was building a package on food version 1.5.6, the first build of a build-right on one, I suddenly realised I've made a problem in 3.com, so I rebuilt it, it's still the same version of a build-right on a package 2, but I've, the new build in the work is a build in 2. So the people here in Stormi differentiate between the two releases of this package. So something that handles now has an exploding package. I'll give you a second one like a bit more just, and you have the information. OK, you remember a client's highlight and include for a reason. The reason I think is very, very important. You can see in the top one we have the root directory, the user bin, user doc, user man, user net, build-right on a package. And the install, the user directory. You can see later on why these are my highlighters, because generally if you look at the conditions on the left-hand side, and the owner and the group, so the user bin, the user bin directory, you can see it's owned by a user doc there. So next, let's just have a look at the, this is the assemble package description. As you saw earlier, when I was doing the install package. So it's basically just a simple package, it's just a simple description. This is another simple package description that contains most of the information you can find about the package. So here it is, it's the suio package. It tells you basically the way in which file you edit your challenge suio. This description is always displayed when you install package. Okay, the other balance of packages, signs of things I've already talked about, is the post-installs range. It's one of the things that they are, are post-installs range, they are not pre-installs range. There's no provision in such-book packages for such-book package management for pre-installs range. So the first one is that you need to install such-doos.sh, because you should be sure that that's all on the previous slide. Generally in this script, we do think that it creates simple links, add new users, do passwords, share them with root files, in the other state package for example. And we also shift coffee files around. So if you install a package that has, say, et cetera such-cru.com, most packages will have a 3.com.u. So when you install it, it doesn't overlap in this new command file that's already installed. So in this script, you've got a new script for the users. If it doesn't finally exist, you've got a new command file, a new command file, a new command file. The second one is the set-up script. This is, so the most common interactive script you don't interact with in that story, just because it's finished. The second script is a cursive base into active script. For such a script like this, you'll find in the attached package, in the 1SSL package. These are basically counter-strips when you need to help configure the package in certain ways. So you never need, in the 1SSL script, you can set up your IP address in the name of the website and so on. These are actually less common when you install the new script. The first script should no longer be used. In fact, it doesn't really work, I believe. It's the one that's just still there. These scripts can be used to only be one mile of options to install them, and they'll have to be between 1993 and 1994 here. And they're now dedicated, and you won't find a single one of these scripts in any package that's made over just that way. So if you just have a look now at the package policies and icons, the main binary directory, the RCHO, is roots in. There's no particular good reason for this anymore. It's based on a really old standard which doesn't actually exist anyway. This is mainly because there's a thing these days, but it's still on the number plate. Sorry. Info, the man's pages, and code modules are usually in service space. Partly links to the versions of soft links. Although some package is just, you'll find that it is in the case, G-Lift C, for example, is born that has many, many hard links. Mainly because it has many hard links. Soft links are converted to shell script code within the build scripts, one of the greatest build scripts. The soft link code in general shell script code is created by the main package program which builds the package, builds the G-Lift file. I'll talk about main package shortly. Staff to cart files, shared objects, and binaries are scripted in general. And per most of the file, per most of the file, as requested, is to be used to shoot this, and to be used to load the file. Chased in old man's pages are used to use a doc if there is a link in that cart file. It's in the service space. What's really worth noting is that the staff to cart uses the satchel USR doc, new file, and new USR map. These are not FHS components. So it's really worth noting that it's about Sackware. Sackware does have a maintained sibling to use a shell to add to your distribution level or keeps these territories. So use a shell doc and use a shell. But in the Sackware package, you will not find documents to use a shell that will be used by doc and user approach. Okay, there's some of the packages that ended with this, because there's really a lot going on. So the application options of our Sackware is a full installation. However, you don't actually need to be a full installation, but I'm not sure there that it doesn't have a full installation of Sackware on it. This is the recommended option which will actually need you to not have a full installation. Does that mean you shouldn't need to be a librarian? No, it's the application of the services. So those tools will not come with the services. And they never will. If you write for those party programmes that can help with the limited solutions to destroy any of the Sackware. But there, in order to really make use of those packages, sorry, make use of those utilities, the package tends to require additional metadata which can be integrated depending on the certain version of the package. Basically the same as every other package tool which is dependency. With the special Sackware packages dependencies are often known in the SackJet file which is the package description. Or in the config files which is especially based on the package which you'll find in the config files this package requires the rest of this task. One of the things in that Sackware as well is that we have some of the most important solutions in the SackJet file in the SackJet file. So if you want to use SackJet if you decide you know better than you need to do that, you can go through and make a system that basically works. This package helps you your system management. It contains some of the most core library systems, as I've said, LitVMG, TerpsCap, NGvSys so that's basically a helper package. Okay. Let's talk about SackJet packages now. Really exciting part of the presentation. This is the section of the presentation. I'm going to cover the method used to build the official SackJet package. I'm not going to talk about the ways that you could build packages. This is just how Patrick talked in business. You should also assume that you've got 100,000 build methods to configure it in the store itself. First, before we do that, let's have a look at what the build script is. My definition is not the build script. A build script is essentially a set of instructions to make files, SackJet file, or the SackJet build script. So firstly we'll prepare a build location such as the directory. A package in the location is also just a directory. We'll remember that these are extract source archives and three of the source from the violence software in some of the components into the package in location. So apply the SackJet package in policies such as CHO group, IGZ, and finally we'll create a primary package. So, before moving on, we'll have to look at the main package. This is a program that actually produces the .DGZ file with our archives. The main package produces the .DGZ in the content of the present work directory. The main package converts soft links into shell strip code, which will go into the install, sorry, the AAB install of the SackJet instance.fm. It doesn't really matter if you check for the .DGZ file as well. So you'll apply the .DGZ file to all of the .DGZ. Although it's very minor, we don't actually have to put it in the .DGZ file, but it's actually similar to the .DGZ file by its price orders. So the normal syntax for .DGZ. That shell is why tells the main package to convert any soft links into shell strip code, and the .DGZ. tells the .DGZ. Sorry, CHO group and CHO model to do that. So the reason you're doing this is because is because if you actually want to make a package to change for the file ownership to the .DGZ you're actually going to be great in the SackJet process. So this is why you always do this. As you can see, I can actually say that you can make a package to convert soft links to shell strip code. You know that you can't do this. You can't include soft links in your package. However, it's working out that it's great to remove package. If you're trying to remove a package that has soft links inside and outside, remove package has no idea that they're there and will leave similar to the .DGZ. So you should always convert the soft links into shell strip code. I don't know if it works to get the soft links to the .DGZ or the file ownership to the .DGZ because you can't convert the .DGZ to shell strip code. You can remove it into an LN. It's a soft link that creates soft links. So there are two different types of package in the builders. Two different types of package builders are in the SackJet. Which I call Clean is a clean package building strips. This package, this build strip, compiles the software and this installs the package content into a build location or a sugo build to be built. And finally, it creates a binary eiddy hitbox. And we have the build strip which I call Dirtly Package Building strips. I'm not going to give you the dirty just to say that we get the distinction between the two. These build strips compile the software or come to the root processor. Just a couple of build links. This is how Patrick does it. This isn't how necessary how I do it at all. Any way I'm going to do it. Packages are always built on disposable birds which are actually to be disposed of. SackJet packages are always built as rich and these packages are always built on a full installation site. Most which in some cases is an additional dependency especially if you have a known install. Most build strips are available between source territories of each package within the sackware source tree. Okay. So this is how I'm going to build the sack. The only way to stack build strips is to produce re-produceable packages. They're simple. They're just simple backshelves. So they don't build pools, and they don't build code and they don't build shell scripts. There's no patch by doing anything on that. The package is the don't scripts are really quiet easy to understand and they're usually less common. The package is over-site built. The package is actually installed into a pseudo-root directory and then they can be built with separate packages Ydw i'n eich cynllun i'r icinol wedi'i ddefnyddio. Felly mae'n gallu gwahanol o'r swath gweldwyr! Mae'n fydd gan edrych, gyda'u cy慶 ar ôl. Felly bydd gydig i'n mynd o'r amhwytaith i'r periwn ar gwrth ynghyn ychydig. Mae'r cyhoeddaint yn ystod o amlwytof, gynnwys. Roedd y gallu cyhoeddus yn dibynnu. Y fan hyn i digwydd yn cynnig o'r cyhoeddaint i'r cyhoeddus yn y swath gweldwyr. Next, I will try to accept the locations, the build locations, so that's the packaging rooms under the attempt to re-publish them. We'll just have to source, configure it, build it, and then install it, even if you're using the SPIR or whatever the name of, honest, so things like the SPIR or the top of the IR or the three depths or whatever. We'll do that, then we'll install the documents into the package, so that it's very particularly useful for those who should be able to do this, to put such advice into this and so on and so forth. We'll set the package in policies, and finally we'll build a package. And the property to build the strict, you simply run it from the source directory within the source directory. We'll do a quick demonstration while building a package. I'm just going to actually build the IMD package. I do accept this one. As you can see, that's basically the package build. The package has been reduced. That's it. You can see that we've run that from the source directory, so you can see that I have any bits, and I have a site based file, which is a package description. So once I've done that, the package is now in slash dmd. And I've been installing this package before, too. So, and then we go. I have now my IMD in my system. I've already wanted it on my body. So, let's have a look now at the other way of building packages. These are the dot build stricts. These are not slack build stricts. These are really scary based on shell sheets. They don't set the site with a package of policies. They install onto the root files. They don't introduce any packages either. They generally use, when the software is a building system, doesn't display any provision for building packages into a pseudo-info location, such as, it doesn't have a best-of-the-power or anything like that. The package is simply too cumbersome, so we still wonder what it is. Gruntily, these build stricts have been phased out of the software, because it's too much of a range in its overhang that you can build in packages using these stricts. In fact, when I checked earlier, the basics version of the software, only has 46 of these build stricts left, minus 40 of them only. There's quite a number of them on. Yes, we've only got 46 of these left, although I agree. So this is a really simple studio example of one of these systems. So I'm sure we all quite familiar with that. They've checked and followed up by re-during it, making it and installing it. Some of them are slightly more complicated than that, but generally that's basically what happens. And again, if you wanted to build and install this, you just room the build strict in the current directory. So, you don't just ask yourself, how do I actually build packages if the build strict doesn't actually build packages? How do I build packages on this? Well, it is a basic process of how I actually build packages, at least. First of all, we have all the stricts and files on the past. We won't adopt build strict in the source directory, and again, to give the same thing a lot, we're going backwards between the two blocks, and basically the difference is, constitutes a package context, more or less, not necessarily more or less. We can't do the differences into the studio root directory. Then we do it between things such as setting the policies and whatever else we want to do. And finally, within the studio root directory, we build packages. We make packages because you talked about it earlier. But maybe think to yourself, this sounds like a nightmare, running all the files on the past. I'm doing it hand to me. This is quite annoying. Patrick doesn't actually do it, he does it like this, but he's actually got a strict called pp, which sounds like a build package. It's an unreleased strict for a good reason. And he's helped you, he knows what the pp does, is gets to these points and does this and stops. He then goes into the directory and does this manually. Again, that's still quite a bit of a manual task. Think to yourself a couple of other things, but I worse actually can't do what they do. And there's a reason why it's not good. So, is there an easier way of building packages from doc.filters? Yes. This is, for example, a slack track, which is one of the utility lines of slack track. If you can see, it's arm slack, which is my slack around board. If you can see arm slack, which is my slack around board. If you can see arm slack, which is my slack around board. Sack track is a utility that only produces a set of files. Sack track can apply all of the known slack track package involved into your package content. And you can build a network package into your software. You can find a slack track in the directory. The way slack track works is it uses an idea for the installation. It still wants to track the installation. So, it basically tracks and makes install. It still wants to have an option, which basically, when something is installed onto the file system, it takes this and it moves it to the creation option or the menu option to create a file in the event. It will not have to be in the event or be in a pseudo directory. So, basically, if you run that one of these doc.filters, you will find slack track. You will find that the package does not install on the file system. It is in the pseudo route and the slack track will insert into the package. However, there is a slight problem with this approach. This is that this approach does not track the slack track by route. So, basically, my resolution, which is basically the same slack track for all the track. All the track is basically all the slack track. It is exactly the same thing apart from it has differences on the file system. I am not going to talk about this, but if you are interested in all the track, there is some documentation on roads which is slack track. All the track itself is just a bit of a script which will find the slack track. Slack track is not a whole list of options. It is not only just a shield that can separate all the tracks. You can even build your own packages just based on simple things. It is not such a big area. There is not a whole number of options such as if you can help the GPT sign or which you can find part of the package because remember we shouldn't have any part of the system on that type of package. Then you can also do other changes. It comes in the post install process so you can glue certain things to the package or actually turn them into the package, the main package. You can do the concepts of the package prior to building something. Let's give you an illustration of what you are doing for the slack track. Basically that is the plan I am going to run. I have told Slack Track to produce a new package for the 806 to the version number 0.16, the architecture I have for 806 and the local model. I have given it the big 806 I have built as a script. This is a really basic script and I will show you that script. You can see how simple the scripts are. You can see how easy it is as far as a patch is all the documents and their text and their policies and the script. Some package built a package but we don't have to do it. Let's just have a look at the actual contents of the group. Let's have a look at the contents of this package. As you can see it is a pretty simple package as well. We have got the user list of the directory. The conditions are set. We have the gysig of the plan pages and we have the slack per package description and we also have the new industry script. The new industry script in this case is because we have some assemblies in the package and the new industry script will recreate the chunk package situation. Then again there will be some assemblies in the cycle plan. It is pretty simple but in general we just want to have a look at the P which would normally be in short the same logic as the policy. I need to do with the filter. That is all you do. It is worth noting that whilst I am saying the slack per package it doesn't always so I am just going to tell you what it is. It is not. With the dot filter most of them are fairly old. We tend to find that Patrick makes a number of changes after he is in short an industry so we don't know what these changes are because they are not often in any way. Generally we tend to not have that many fixes but he will do things such as remove the files or remove the files in different ways which we have no idea about because he doesn't actually have any differences between what slack packages he has and what slack per package he needs. So generally because he doesn't have a load he is playing that. We will finish off with a quick checklist that we were interested in. Do you remember that the slack per directory location is on FHSD5 so that is to use a dot directory that you are interested in. Those are the most important assets. The install slash slack less package instruction part is 30 lines maximum. Most things 11 is not actually working. And he said that if you don't have any package you just take a template and it's not a great source. That's why I just wrote a copy of it as easy as I do because it actually happens on hand when you open a package. So trying to do that is when building packages when they install a package they built they find that the package description gets played. And generally this isn't the way the title is packaged then. Actually as you saw in a previous slide it shouldn't package named codon and any information about that package. And simply you can find that they've met how that's going to work and that's generally the way it's going to work. With the install script with the FHS script you don't need any of these relatively package names. So that means that you don't just assume that you're building a directory because what happens is when you package is for example joining out installation and having it by installing into a studio root they're not installed over the installed area. So what happens is when the install package sees these into a studio root extracts them and it assumes that studio root is directly you can specify a separate root directory so you can install a new root and install that is why it shouldn't be built after that. Your script should generally also be actually compatible. This is because the installer uses that as its base although for yourself you can use where you want to be able to use your cache which is generally a script that you check out and it's generally mined as a shared library so it's up to you that you don't have to especially if it's written in a way. That's generally what happens when you install it. The permission ownership is very much if you're building a package you should always make sure that your package is root directory is CH1755. It should be CH1755 some people have problems if they build your own packages and the directory is not 755. If there's anything else that you want to do you'll use it when you get to login. So make sure that you set your package to the directory and also you should probably root code in your final version. That places should be Gbit and you can repair any broken obstacles if you make any. And finally, if you wanted to if you were rebuilding a separate package an official one just do a bit between the two and see if yours has inherited any files that shouldn't be there or is missing any files that shouldn't be missing. So in summary, cycle of build scripts are similar to last scripts with a dot build being generally placed out as soon as possible. The build scripts are available on the cycle of build scripts and I've tried to keep this presentation between my level but you know it's just for sure. I have written an overview document which is included in the cycle path which goes far more in depth especially into the cycle of building system than I could possibly do in presentation. So I'd like you to read that if you're interested in learning more on this. That's it. That's the question. You said that in the domains that there should be should be relative from relative to us to those Yes, absolutely. In other words, so I'll look at the one I don't want to quickly look at the number but they can see it so it's relative in fact that it doesn't do cd4 as actually as I'll be just a cd8 user there because it assumes that the cd8 the cd8 user is actually just an example just extracts so the reason is if you install the witness into by install it's happening into a separate directory and you use that to environment you go and actually modify my group file system rather than the other directory to install it That's it. When this group is started it's in the zone or the factory group When you install package actually it's actually just there that's what happens when cd root and you go to the shell script where the parameters are actually stored that's what I'm actually reading so if you use that to environment you can install it from the environment system and you actually want it to show it to the environment Does that explain that? Any other questions? Do you know what the philosophy is about computing to create dependent package dependencies? Create dependencies? Because while designing it's like a dependency checking a resolution is a deliberate design choice it's not a problem or anything Patrick doesn't want to include dependencies and it's most likely to never work because as I said earlier this recommended option of installing stackwares is to install a full system which means that if you install a full system stackwares you'll never have any dependency problems because unless you're installing the third part of languages You just like to give it a simple I personally don't care to all dependencies I don't need them The idea of stackwares is simple yet you also got to actually put some effort into learning how Leverton Unix works I know it's probably easiest ever to learn in some respects but there are tools available if you wanted to you could actually show you the more great idea In stackwares we have a system of stackwares in stackwares we have a file called the manifest file in this manifest file it lists every single package in stackwares so if you use LDP for example to find a library a shared library for whatever you could see if any sort was missing you could look at this manifest file and find it as you can see it lists every package so you can actually just do this manually it's a manual process but it's the way you can do it constantly manually as I said during the course of the presentation there are other things such as the squarrade which can help you basically help you with the dependency resolution before I remember why the squarrade uses its manifest in order to do this but actually it just wants to get a stackwares simple because it is a simple distribution it doesn't do any it doesn't basically get in the way if you want to do a new batch on your window system I can do it now on that type of PLO I can do whatever I want to basically how do you solve it if you use it as a way to do it anyway that's the way it's done I think it's probably following the same question whether you answered it but if you say there is a different package as always versus a reference of the full installation so the definition of a full installation is a combination of manifest now meaning any installation has come on before CD1 now meaning distribution meaning version is likely before CD1 defines the reference so I was going to say actually it's like where it comes from before CD2 contains the source basically the manifest for example this one this manifest file is in the roots of the stackware directory so we have a long CD more than 2 I'm not actually sure but when the CD's are built they just contain a certain number of these which everyone will sit on to do but the manifest file contains every single package available if it doesn't contain you don't understand the manifest file that needs to be made you're not saying this one you're saying we're through such a current we can define what the definition is that's the manifest file yes, the content of the manifest contains the process of every single package it's always in this directory so it's open it's just in lines in such a current you can have as far as the source is so that's the way you define the manifest yes for this you've been calling this stackware with the all the way for example, I think about books that is written in a way and all you can do is handle this because this is a screen that you can use sorry sorry but I think it's when you install the last tool that all the time you can run don't have to give your mind to create something that may be installed that you have to look at so that you can look at this I think, for example, of a book or you can read for example books such a current doesn't actually have what you would look at so if I just put the code on so if I say I should go to that right, there we go very much to see if you want just to look at it so in fact it doesn't pair what it also uses so what is it called oh I'm sorry well I guess you can package books with that as you can see it set the positions and it's set the ownership and also you can notice that you've actually used the input I don't think that the old stackware style doesn't pair up because there's a person that also used to leave my stack in and I'll stack that as well so again it's a bit of a check but I'll stack back the idea of the sort of stackware philosophy don't get it in the worst if you don't want to use it so you've just been on the answer again at all I don't know what you mean by that but you've got a certain reason why you don't use it so someone who also uses ARPN but you've very much liked the simplicity which do you prefer have you seen my ARPN books? one of my spec files for ARPN is what it's like to have a model of antheism but for a sample of it I don't know I actually had to look at the ARPN website and go to the book presentation and run around the village I looked at the system and looked at the things that I was adding and saw the thing I needed to do but it's one of the things a few of the most happy things is to use the build stress I suppose all the things down don't have the ability to change the user I wonder if this has got to be installed before the build otherwise it will fail the reason why I'm doing that is because of the tendency so whatever you want to call it but again I think it's quite a simple take off because I want to have some mystery so that's how I was in with the previous talk about the suggestion why isn't party-and-sys into something that just does the inspiration like separate from all the evidence so if it's possible to go into the evidence yet we have a question for my um some other plan so that's that's actually the package this is the build this is the not the script for what it wants to bash for arm slack I said before arm slack is my unofficial order of slack to the arm because when I started porting I am going to prove what depending on what so when I built it I ended up with either some functionality or it's up and it didn't work for so here I actually extended the real system to included that in the patch library so here you can see I was doing a dependency jet to make sure that the relish that the patch actually needs is installed before I install the patch it's in some way not quite like it because it's quite handy especially if I want to do thoughts out of those to my animals which I might do in this case but it depends it's not quite like the system because I can't remember anything but if I look at my script I can see what it depends on and I know which is that my needs are actually compiled and it's still before I can build the set of things so I mean I actually do come on and it's easier than most of the lots and lots that can handle my questions as well yeah the board is so exciting I don't think it's a good function I don't think it's a good way to I agree with the balance I would argue that as I say it's just a cosmetic thing it's a matter of thought you don't need to do any thing it's actually there's a problem with that actually I'll show you that's just one of the needs it needs to be something else it needs to be something else that's right it needs to be like something else there's actually a deal going on has that his supports actually taken the power back it's just not a challenge when it's just a cosmetic的 it doesn't know generally if you're distributing a package would be right you shouldn't move away from the recover within the individual text belogic that's a must i've seen people produce package