tools/manjaro-tools

Fork 0

I switch kinda doesn't work #216

New issue

Closed

opened 2016-05-15 11:24:34 +00:00 by philm · 11 comments

philm commented

2016-05-15 11:24:34 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

If I check mkchrootpkg I find this line: [[ ! -f PKGBUILD && -z "${install_pkgs[*]}" ]] && die 'This must be run in a directory containing a PKGBUILD.'. So we have to recheck that option on how we want to use it. I suggest it like this:

buildpkg -p kpmcore-dev -i

This will say to buildpkg that I want to build it, install it to the chroot and then move it to the cache dir. We can use some like pacman -U kpmcore-dev-<VERSION>*z -r <PATH/TO/CHROOT>.

*Created by: philmmanjaro* If I check **mkchrootpkg** I find this line: `[[ ! -f PKGBUILD && -z "${install_pkgs[*]}" ]] && die 'This must be run in a directory containing a PKGBUILD.'`. So we have to recheck that option on how we want to use it. I suggest it like this: `buildpkg -p kpmcore-dev -i` This will say to **buildpkg** that I want to build it, install it to the chroot and then move it to the cache dir. We can use some like `pacman -U kpmcore-dev-<VERSION>*z -r <PATH/TO/CHROOT>`.

philm commented

2016-05-15 13:40:50 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

I think ou confuse -i with -n flag.

    -n                 Install and run namcap check

as opposed to

-i <pkg>           Install a package into the working copy of the chroot

*Created by: udeved* I think ou confuse -i with -n flag. ``` -n Install and run namcap check ``` as opposed to ``` -i <pkg> Install a package into the working copy of the chroot ```

philm commented

2016-05-15 22:20:42 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

@udeved: at the current situation you can't install any package using the -i switch into the chroot. the -n switch will install the package to your host.

*Created by: philmmanjaro* @udeved: at the current situation you can't install any package using the -i switch into the chroot. the -n switch will install the package to your host.

philm commented

2016-05-15 23:54:42 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Strange that. It used to work, and had no complaints before.
Must have been introduced lately I think.

*Created by: udeved* Strange that. It used to work, and had no complaints before. Must have been introduced lately I think.

philm commented

2016-05-15 23:59:36 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

buildpkg -p kpmcore-dev -i

This will say to buildpkg that I want to build it, install it to the chroot and then move it to the cache dir.

If you want to use it like that, what is the difference to -n switch then?
Do we misunderstand each other? You want -i for -n ? We got exactly what you ask on -n.

-i [pkg_name.pkg.tar.xz] should be the current way to install a non repo depend package in chroot.

*Created by: udeved* ``` buildpkg -p kpmcore-dev -i ``` > This will say to buildpkg that I want to build it, install it to the chroot and then move it to the cache dir. If you want to use it like that, what is the difference to -n switch then? Do we misunderstand each other? You want -i for -n ? We got exactly what you ask on -n. -i [pkg_name.pkg.tar.xz] should be the current way to install a non repo depend package in chroot.

philm commented

2016-05-16 00:50:48 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Ok, with buildpkg -p kpmcore-dev -i I want to build the package and install it after in the chroot, or is it already possible and I missed it?

*Created by: philmmanjaro* Ok, with `buildpkg -p kpmcore-dev -i` I want to build the package and install it after in the chroot, or is it already possible and I missed it?

philm commented

2016-05-16 06:15:37 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Yes, what you want is -n switch already if I understood you correctly.

*Created by: udeved* Yes, what you want is -n switch already if I understood you correctly.

philm commented

2016-05-16 11:23:08 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

ok, what does the -n switch? Build the package and install it on the host, or build the package and install it into the chroot? If it is the later, it is fine for me, then the -i switch needs to be checked to install a package manually into the chroot. If it is the first, then why do we check the package on the host?

*Created by: philmmanjaro* ok, what does the -n switch? Build the package and install it on the host, or build the package and install it into the chroot? If it is the later, it is fine for me, then the -i switch needs to be checked to install a package manually into the chroot. If it is the first, then why do we check the package on the host?

philm commented

2016-05-16 12:57:07 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Both -n and -i will install in the chroot.
We do not have an option to install on the host, because I always planned that this will get automated.
We wouldn't need an option to install on host, which is a build server.

We really need some direction here, and a prospect.
I think a build server should be absolutely manjaro's next goal.

*Created by: udeved* Both -n and -i will install in the chroot. We do not have an option to install on the host, because I always planned that this will get automated. We wouldn't need an option to install on host, which is a build server. We really need some direction here, and a prospect. I think a build server should be absolutely manjaro's next goal.

philm commented

2016-05-16 13:00:24 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

@udeved: yes, we are working on a plan to get a build server. So if -n is also installing into the chroot. I'm fine with it. However we should check the -i switch once again. I didn't get a package installed with it lately. Maybe I miss some ...

*Created by: philmmanjaro* @udeved: yes, we are working on a plan to get a build server. So if -n is also installing into the chroot. I'm fine with it. However we should check the -i switch once again. I didn't get a package installed with it lately. Maybe I miss some ...

philm commented

2016-05-16 13:03:54 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

How did you use the -i switch?

I have only tested it once, after kirek requested this feature to install depend packages in chroot.

Should be something like

buildpkg -p foo -i /path/to/bar.pkg.tar.xz

*Created by: udeved* How did you use the -i switch? I have only tested it once, after kirek requested this feature to install depend packages in chroot. Should be something like buildpkg -p foo -i /path/to/bar.pkg.tar.xz

philm commented

2016-06-06 18:56:52 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved