[Question] -I and -b about blackarch-devtools HOT 9 CLOSED

install the packages you specify

Ah! so -I is like -b but with some "install other deps".

from blackarch-devtools.

Also please bump to new version (see releases) that build packages in .tar.zst format, very faster. (You need to delete the current blackarch_chroot dir and recreate it, see the release notes).

from blackarch-devtools.

Also please bump to new version (see releases) that build packages in .tar.zst format, very faster. (You need to delete the current blackarch_chroot dir and recreate it, see the release notes).

I sure will do that

from blackarch-devtools.

Hello, @noraj . What are you trying to do? The -I option works in the following way: install the packages you specify there in the clean chroot environment, then build the package of the PKGBUILD in the current dir but doesn't install it.

In short, if you use -I you don't need to use -b, just -I and -b is assumed for PKGBUILD in the current dir.

from blackarch-devtools.

Scenario:

I'm packaging package A, but package A has a dependency package B that is not in AL or BA so I package it too.

So when I want to build package A with blackarch-devtools the package B dependency is not satisfied and I don't know how to do so.

from blackarch-devtools.

Scenario:

I'm packaging package A, but package A has a dependency package B that is not in AL or BA so I package it too.

So when I want to build package A with blackarch-devtools the package B dependency is not satisfied and I don't know how to do so.

You just need to:

Go to directory of A package, run blackarch-devtools -I path/to/package-B.tar.zst. package-B will be installed in the chroot environment then package A will be build.

from blackarch-devtools.

$ blackarch-devtools -u
$ cd packages/perl-encoding-ber
$ blackarch-devtools -b
$ cd ../../packages/rdp-sec-check
$ blackarch-devtools -I ../perl-encoding-ber/perl-encoding-ber-1.02-1-any.pkg.tar.xz
$ blackarch-devtools -t -e rdp-sec-check -p rdp-sec-check-9.5956857-1-any.pkg.tar.xz

All good ✔️ Thanks

from blackarch-devtools.

For documentation you can choose an easy doc tool like https://docsify.js.org/#/ that doesn't need compiling, you deploy it in /docs like I did for this tool https://github.com/Orange-Cyberdefense/haiti/tree/master/docs and you serve it with github pages so you don't need a CI to build the doc.

Then I'll be able to help you creating content for the doc :)

from blackarch-devtools.

For documentation you can choose an easy doc tool like https://docsify.js.org/#/ that doesn't need compiling, you deploy it in /docs like I did for this tool https://github.com/Orange-Cyberdefense/haiti/tree/master/docs and you serve it with github pages so you don't need a CI to build the doc.

Then I'll be able to help you creating content for the doc :)

I will have in in mind. Thanks.

from blackarch-devtools.