![]() |
|
||||||||||||||||||||||||||
ForumWed Feb 5 00:42:31 2025 UTC
Help:
Cards: The Package Manager
![]() Mon Feb 3 16:37:02 2025 UTC
Help:
Cards: The Package Manager
![]() Mon Feb 3 00:02:45 2025 UTC
Help:
Cards: The Package Manager
![]() Sun Feb 2 05:04:23 2025 UTC
Help:
Cards: The Package Manager
![]() Mon Jan 13 10:12:36 2025 UTC
Help:
General
![]() Mon Dec 16 08:41:36 2024 UTC
Help:
General
![]() Wed Nov 27 11:18:31 2024 UTC
Help:
General
![]() Sun Nov 24 14:26:31 2024 UTC
Help:
General
![]() Mon Nov 18 18:43:34 2024 UTC
Help:
General
![]() Wed Nov 13 08:34:40 2024 UTC
Help:
General
![]() |
Mon Feb 10 20:18:46 2025 UTC "mybld" command setupContentsImportantAll the commands are enter via your account. It means no need to use the root account. Once the GIT project is recovered, all manipulations MUST be done from the folder containing your GIT project. SetupTools (packages to install)It is assumed that your NuTyX is free from any development package. So we start by installing the utilities: get rsync git Get the GIT projectWe start by cloning the GIT project containing all the NuTyX recipes: git clone -b <branch> https://github.com/NuTyX/packages-x86_64.git <branch>The variable <branch> can take testing or rolling as value. Once the GIT project in place, we move to the root of it, indeed the command mybld uses information from the GIT (VERSION, USERNAME, EMAIL, etc). Go to the root of the projectThe GIT project is cloned. We need to go to the root of it.cd <branch>
From now on all the followings commands are launched from the actual folder.
Setup my name and emailThis step is necessary if you want to share your new packages, indeed, the mybld -n command uses this information when creating your new package.git config --global user.name "James Bond" git config --global user.email "james@nutyx.org" Implementation of working directoriesThe mybld command uses a set of folders for its operation, they must therefore be created using the command: mybld -I You can adjust the operating folders locations in the configuration file ~/.mybld via the variables ROOT, ROOTMOUNT and VERSION. Available CollectionsChoose the collection you want to work on. Depending on the collection chosen, you will need to retrieve the collections specified in the right column.
Retrieving binaries collectionsDepending the choose collection, launch the command: mybld -s name_of_collectionto retrieve the collection(s) needed. For example, to use the gui collection, run the command: for i in base cli gui; do mybld -s $i;done You can specify a custom address and version in the ~/.mybld configuration file via the URL and VERSION variables. Using the command(Re)Compile a package
mybld name_of_packageCompilation begins immediately. Increment the version and recompile a package
mybld -i name_of_the_packageAfter confirmation, the compilation start immediatly. Advanced modeLet's say we have a critical package that doen't want to build properly. In that case, the best way is then to use the -p option for pause.To illustrate the purpose of --pause option, I will try to compile nftables Entering into the chrootmybld -p nftables You are now in chroot. Type exit when finish. Good luck !!! Where is whatThat's now the big question.
Go on with compilationSo let's give a try to compile nftables now. Just type:cards create nftablesCompilation with start just like normal. If an error occur now, it will just return to the prompt: checking for LIBMNL... yes checking for LIBNFTNL... no configure: error: Package requirements (libnftnl >= 1.1.8) were not met: No package 'libnftnl' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables LIBNFTNL_CFLAGS and LIBNFTNL_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. =======> ERROR: Building '/DEPOT/cli-extra/nftables/nft....cards.tar.xz' failed. cards 3.1.0 create: could not parse Pkgfile: While running 'build()' Fix the issueWe can now fix the issue by adjusting the deps:cards install libnftnl libnftnl.develWe go to the working directory and we give another try : cd /tmp/work/src/nftables-0.9.7 ./configure --prefix=/usr \ --sysconfdir=/etc/nftables \ --mandir=/usr/share/man \ --with-jsonLooks beter. nft configuration: cli support: readline enable debugging symbols: yes use mini-gmp: no enable man page: yes libxtables support: no json output support: yes enable Python: yes (with /usr/bin/python)We can now continue the rest of the pkgfile commands: makethe last command in Pkgfile is: make DESTDIR=$PKG installPKG variable need to be assign to /tmp/work/pkg: PKG=/tmp/work/pkgtime to finish: make DESTDIR=$PKG install install -Dm644 ../nftables.conf "$PKG/etc/nftables/nftables.conf" Packing upwhen Pkgfile is complete, we can go back to the Pkgfile directory and use the command pkgmk -po to finish the job:cd /mybld/rolling/cli-extra/nftables/ pkgmk -po HelpThe mybld command allows all kinds of options. mybld -h Remember to consult mybld's man page to obtain more information about other possible options: man mybld |