Bug#803057: Npgsql package

OK, thanks for the explanation, that makes sense.

I'm not at all familiar with what you guys intend to do with NuGet from a Debian perspective. If this is more of a short-term backwards-compatibility measure, may I suggest not publishing Debian packages for Npgsql 3.x to force people to move to NuGet? This would make sense from a purely .NET/NuGet perspective, and the move from 2.x to 3.x is a major one in any case.

On Mon, Oct 26, 2015 at 5:58 PM, Jo Shields <directhex@apebox.org> wrote:

NuGet introduces a number of packaging issues that we are not ready to
deal with yet from a dependency resolution perspective in Debian (we
have some measures half implemented to handle it).

Uploading from the 2.x branch is a short-term measure to satisfy
dependencies on packages which currently build with -r:Npgsql but fail
with Mono 4.0 since that bundle is gone

On 26/10/15 15:54, Shay Rojansky wrote:
> Hi.
>
> I'm the maintainer of Npsgql, and I happened to see this report.
> Npgsql was removed from mono because it was severely out of date, and
> in today's .NET world the best practice is to install packages via
> nuget rather than installing them on the system (i.e. in the Global
> Assembly Cache or GAC). Is there a Debian policy about making .NET
> packages available as GAC-installing packages?
>
> All this aside, the latest version of Npgsql is now 3.0.3 and not
> 2.2.7 which is apparently what's being published as a Debian.
>
> Shay

--
To unsubscribe, send mail to 803057-unsubscribe@bugs.debian.org.