When I try to install dotnet-sdk-bin 5.0.4 in Manjaro from AUR I get this: "target not found: dotnet-sdk-bin", should I wait till dotnet-core-bin is in AUR?
Search Criteria
Package Details: aspnet-targeting-pack-bin 9.0.4.sdk203-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/dotnet-core-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | dotnet-core-bin |
| Description: | The ASP.NET Core targeting pack (binary) |
| Upstream URL: | https://www.microsoft.com/net/core |
| Keywords: | .net dotnet microsoft |
| Licenses: | MIT |
| Conflicts: | aspnet-targeting-pack, aspnet-targeting-pack-9.0 |
| Provides: | aspnet-targeting-pack, aspnet-targeting-pack-9.0 |
| Submitter: | Gr3q |
| Maintainer: | Gr3q |
| Last Packager: | Gr3q |
| Votes: | 47 |
| Popularity: | 0.39 |
| First Submitted: | 2019-10-02 17:13 (UTC) |
| Last Updated: | 2025-04-17 07:37 (UTC) |
Dependencies (1)
Required by (10)
- dotnet-sdk-6.0-bin (optional)
- dotnet-sdk-7.0-bin (optional)
- dotnet-sdk-8.0-bin (optional)
- dotnet-sdk-bin
- iceshrimp.net (requires aspnet-targeting-pack) (make)
- iceshrimp.net-git (requires aspnet-targeting-pack) (make)
- iceshrimp.net-pre (requires aspnet-targeting-pack) (make)
Sources (4)
servimo commented on 2021-03-11 19:00 (UTC) (edited on 2021-03-11 19:01 (UTC) by servimo)
Gr3q commented on 2021-03-11 08:23 (UTC)
You might be talking about the .NET Framework, the framework running WinForms applications. The normal .NET is .NET Core for a while now (renamed simply as .NET)
k8ie commented on 2021-03-11 08:13 (UTC)
Wow, maybe not actually. I remember dotNET being proprietary, while dotNET Core was supposed to be FOSS. Now I'm not really sure. It looks like Microsoft released dotNET as FOSS.
k8ie commented on 2021-03-11 08:09 (UTC)
@Gr3q One thing to note is that the packages in the repo are dotNET Core, not dotNET. Normal dotNET is currently at version 5, while dotNET Core is at version 3.1.
AFAIK they are two different things, but often it doesn't matter which one you choose.
Gr3q commented on 2021-03-11 07:55 (UTC)
The purpose of depending on netstandrad-targeting-pack-2.1 is that you have an option either user netstandard-targeting-pack or netstandard-targeting-pack-bin with the AUR packages.
I don't support using the AUR packages along with the official packages because I can't guarantee that they are up to date (as you can see they are on version 3.1 instead of 5).
My recommendation is to use one or the other, because it is more likely to break if they are mixed than not.
amos commented on 2021-03-10 12:39 (UTC)
Well, both dotnet-sdk and and dotnet-targeting-pack (from the official repos) require netstandard-targeting-pack (and not netstandrad-targeting-pack-2.1), and this is not provided, which creates a conflict. I didn't mean to remove the provides of netstandrad-targeting-pack-2.1, just to add the provides of netstandrad-targeting-pack.
Regardless, netstandard-targeting-pack-bin can be safely removed from conflicts and provides, as this is already the package name itself (and is not depended on by anybody).
Gr3q commented on 2021-03-10 07:43 (UTC)
The official package name is netstandard-targeting-pack, but it actually provides netstandard-targeting-pack-2.1.
This package provides netstandard-targeting-pack-2.1 and itself, so it's conflicting the package in the official repos as intended
amos commented on 2021-03-09 19:32 (UTC)
I assume the conflicts and provides were meant to be netstandard-targeting-pack and not netstandard-targeting-pack-bin?
Alkaris commented on 2021-02-04 19:28 (UTC)
Cannot install this package because it gives target not found: dotnet-sdk-bin
patstew commented on 2020-09-10 22:03 (UTC)
The arm builds don't work at the moment because of the linux-x64 reference in package_dotnet-targeting-pack-bin. I've uploaded a fixed PKGBUILD here: https://pastebin.com/rMv3PAR5
Pinned Comments
Gr3q commented on 2019-10-05 07:28 (UTC) (edited on 2021-02-13 09:06 (UTC) by Gr3q)
IMPORTANT INSTALLATION INFO (a reminder for myself as well):
For dotnet to work you need to EXPLICITLY install:
If you keep the install order in mind and you don't rely on pacman to resolve your dependencies you will be fine.
Longer explanation:
Every dotnet-sdk is dependent on a specific version of dotnet-runtime, this is built into dotnet.
Technically you only need the latest dotnet-sdk because it can build to any earlier versions.