Package Details: netstandard-targeting-pack-bin 9.0.0.sdk100-1

Git Clone URL: https://aur.archlinux.org/dotnet-core-bin.git (read-only, click to copy)
Package Base: dotnet-core-bin
Description: The .NET Standard targeting pack (binary)
Upstream URL: https://www.microsoft.com/net/core
Keywords: .net dotnet microsoft
Licenses: MIT
Conflicts: netstandard-targeting-pack, netstandard-targeting-pack-2.1
Provides: netstandard-targeting-pack, netstandard-targeting-pack-2.1
Submitter: Gr3q
Maintainer: Gr3q (natep)
Last Packager: Gr3q
Votes: 43
Popularity: 1.25
First Submitted: 2019-10-02 17:13 (UTC)
Last Updated: 2024-11-13 09:45 (UTC)

Dependencies (0)

Required by (17)

Sources (4)

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:

  • ONE dotnet-host - highest version possible
  • ANY NUMBER of dotnet-runtimes (and its sdks after if you want to build as well - Right now version 'bin', '3.1', '3.0', '2.2' and '2.1' are tested to work together)

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.

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 Next › Last »

CruciformHawk7 commented on 2020-05-16 15:35 (UTC)

Hello,

When I upgrade the package, I get failed to prepare transaction (conflicting dependencies: dotnet-runtime-bin). I have removed dotnet-* packages and the issue still persists.

Gr3q commented on 2020-01-16 09:41 (UTC)

I get it now, thanks

huupoke12 commented on 2020-01-16 09:39 (UTC)

Isn't this is obvious? To let other packages know what these packages provide and for easy version comparison. Example: A package that only requires the dotnet runtime later or equals to 3, this can be easily be described with dotnet-runtime>=3 in the PKGBUILD. The official one is fine with this, but not with this package is not since it only provide dotnet-runtime-3.1 but not dotnet-runtime, so it can't be recognized and compared. Another example is a package that don't have this requirement, any version of dotnet runtime is fine.

Gr3q commented on 2020-01-16 09:15 (UTC)

I'm happy to add it to the array, but could you explain it to me what is the benefit of doing this?

huupoke12 commented on 2020-01-16 08:46 (UTC) (edited on 2020-01-16 08:48 (UTC) by huupoke12)

The packages should add to their provide array with their corresponding version like: provides=('dotnet-sdk=3.1.1.sdk101'), or use with variable: provides=("dotnet-sdk=$pkgver") (the official ones don't need to do this because they are implicitly added with their package name and version)

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:

  • ONE dotnet-host - highest version possible
  • ANY NUMBER of dotnet-runtimes (and its sdks after if you want to build as well - Right now version 'bin', '3.1', '3.0', '2.2' and '2.1' are tested to work together)

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.

riscie commented on 2019-10-04 14:18 (UTC)

Thank you again @Gr3q!

Gr3q commented on 2019-10-04 12:01 (UTC)

@riscie the community package will be updated as far as I know, it is in the works.

The purpose of this package was that I could use dotnet on armv7f architecture as well, what is missing from the repos.

riscie commented on 2019-10-04 09:09 (UTC)

Hey @Gr3q thank you so much for your work. It seems with the help of your effort we no have a way to use dotnet core 3.0 on arch. Does that mean the community packages of dotnet will no longer be updated? They were flagged out-of-date quite a while ago.

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 Next › Last »