Debian's build servers have no internet access, by design (as is the
case for most distros). Packages requiring internet access to build
don't go into Debian, full stop. So if their build system needs it, then
there needs to be provision for using a local cache instead of the web
(NuGet supports th
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 Nu
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 b
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).
4 matches
Mail list logo
