What port does rust install?

[bagas]

Hello.
How to know which port of rust is being installed?

# pkg version -v | grep "rust"
rust-1.63.0 < needs updating (index has 1.64.0)

 

[SirDice]

Look at pkg info -o rust. The 'origin' is the port name.

 

[bagas]

pkg info -o rust

# pkg info -o rust
rust-1.63.0 lang/rust

no information.
I'm interested in which port rust installed by dependency.

 

[SirDice]

So, now you know the package rust was built from the port lang/rust.

 

[bagas]

So, now you know the package rust was built from the port lang/rust.

This is clear, I'm interested in which port rust installed by dependency.

 

[SirDice]

pkg-info(8):

     -r, --required-by
             Display the list of packages which require pkg-name.

     -d, --dependencies
             Display the list of packages on which pkg-name depends.

 

[bagas]

pkg info -d lang/rust
rust-1.63.0:
curl-7.85.0

I did not find in the curl port how to disable rust support.
I need to get rid of rust in the system.

 

[SirDice]

I did not find in the curl port how to disable rust support.

Wrong way around. It's rust that depends on curl. You're looking for ports/packages that have a dependency on rust, so look at pkg info -r rust.

 

[bagas]

Wrong way around. It's rust that depends on curl. You're looking for ports/packages that have a dependency on rust, so look at pkg info -r rust.

# pkg info -r rust
rust-1.63.0:

Looked, no information.

 

[SirDice]

Then nothing is depending on it. Unless you actively installed it yourself (non-automatic) it will probably get removed with pkg-autoremove(8).

 

[bagas]

Then nothing is depending on it. Unless you actively installed it yourself (non-automatic) it will probably get removed with pkg-autoremove(8).

No, it was installed by dependencies.
I'll try pkg-autoremove.

 

[cy@]

Hello.
How to know which port of rust is being installed?

List the rust packages installed:

slippy$ pkg info -I rust\*
rust-1.64.0                    Language with a focus on memory safety and concurrency
rust-cbindgen-0.24.3           Generate C bindings from Rust code
slippy$

Tell us their origins:

slippy$ pkg info -o rust\*
rust-1.64.0                    lang/rust
rust-cbindgen-0.24.3           devel/rust-cbindgen
slippy$

Tell us which package installed the rustc command:

slippy$ pkg which `which rustc`  
/usr/local/bin/rustc was installed by package rust-1.64.0
slippy$

 

[SirDice]

No, it was installed by dependencies.

It may have been a build dependency. Packages don't record build dependencies because those are only relevant when building a port.

 

[bagas]

pkg-autoremove(8).

So it deletes almost all software installed on the server.
pkg-autoremove
Deinstallation has been requested for the following 113 packages

 

[VladiBG]

Did you mix ports with pkg?
You can first check what programs (pkg / ports) you need to have by view the prime origins ( pkg prime-origins) then if none of them is removed by pkg autoremove then you are safe to remove all old orphaned dependencies.

Note:
Those 113 packages (ports) are left overs from some program that was installed then removed. It's best practice to issue pkg autoremove after every pkg/port removal so it can remove (cleanup) the old depenancies of already removed program.

For example if you install mod_php80 it will install php80 as dependency but when you delete mod_php80 it will not remove the php80 so to clean it you use pkg autoremove.

Note2:
If you are using ports during the build process the ports install build dependencies and if those build dependencies are not changed during the next upgrade of the port you may want to keep them instead of cleanup with pkg autoremove as this will speed up the next build port. But this is true if only upgrade your ports on very short interval like once per week and no new version of the build dependencies is released.

 

[bagas]

Did you mix ports with pkg?
You can first check what programs (pkg / ports) you need to have by view the prime origins ( pkg prime-origins) then if none of them is removed by pkg autoremove then you are safe to remove all old orphaned dependencies.

I installed all ports from /usr/ports/.
Updated with portupgrade

 

[VladiBG]

Just compare the prime-origins with the ports that pkg autoremove wants to cleanup. If none of prime origins is removed and you don't recognize any port that you need from the autoremove list then it's safe to clean it.

Note:
Instead of spending time and build those ports on the server itself i would suggest to take a look at synth(1) it's very easy to create your own repository on another server and use to binary update your server(s) and it's more safer as this will eliminate the risk of temporary fail to build ports due to some recent vulnerability or broken port.

 

[bagas]

Removed the software with pkg autoremove -y.
deletes (cargo-c|rust|.....)
I run libgd port updates.

---> Building '/usr/ports/graphics/gd'
===> Cleaning for libimagequant-4.0.4
===> Cleaning for cargo-c-0.9.8_6
===> Cleaning for rust-1.64.0

I see that software (cargo-c|rust|cmake-core|.....) is being built on a new basis.
Why it was then to remove this software I do not understand.

 

[VladiBG]

those are build dependencies not directly for libgd but for some of the other ports that libgd requires. If you want to dig down it's easy to fetch the ports index and make all-depends-list
check ports(7) for more info

 

[laurentis]

Removed the software with pkg autoremove -y.
deletes (cargo-c|rust|.....)
I run libgd port updates.

I see that software (cargo-c|rust|cmake-core|.....) is being built on a new basis.
Why it was then to remove this software I do not understand.

graphics/libimagequant has been rewritten in rust. If you check the Makefile of graphics/gd, you'll find that you can remove this dependency by turning off the option LIQ.

 

[bagas]

Same version (PHP 7.4.32) on both servers.
Both servers have php module gd.

php -m | grep gd
gd

Installation on both servers came from /usr/ports/.

pkg version -v | grep "libimagequant"
libimagequant-4.0.4 = up-to-date with index

pkg prime-origins | egrep 'php|gd'
graphics/gd
lang/php74
lang/php74-extensions

# pkg version -v | grep "gd"
libgd-2.3.3_2,1 = up-to-date with index
php74-gd-7.4.32 = up-to-date with index

on another server

# pkg version -v | grep "libimagequant"
libimagequant-2.17.0 = up-to-date with index

pkg prime-origins | egrep 'php|gd'
lang/php74
lang/php74-extensions

pkg version -v | grep "gd"
libgd-2.3.3_2,1 = up-to-date with index
php74-gd-7.4.32 = up-to-date with index

Why then in one case version 4.0.4 was installed in another ver.2.17.0?

 

[Jose]

Why then in one case version 4.0.4 was installed in another ver.2.17.0?

You updated the ports tree more recently on one server?

 

[bagas]

You updated the ports tree more recently on one server?

Before each software update, I update the ports on the servers and rebuild the indexes for the ports.

 

[Jose]

Before each software update, I update the ports on the servers and rebuild the indexes for the ports.

How? Git? If so, is one server on the quarterly branch?

 

[richardtoohey2]

graphics/libimagequant has been rewritten in rust. If you check the Makefile of graphics/gd, you'll find that you can remove this dependency by turning off the option LIQ.

As soon as I saw this recent update wanting to build and install cargo I knew rust wasn't far behind so I stopped the update and changed the config options for gd.

But it seems more and more is being re-built with rust so at some point I'll have a critical dependancy on rust and be forced to do things differently.