-
Notifications
You must be signed in to change notification settings - Fork 109
Conversation
1625819
to
165f4d7
Compare
@@ -0,0 +1,30 @@ | |||
{ | |||
"maintainer_name":"Microsoft", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Eilon Please review this debian config file. This is mostly copied over from https://github.com/dotnet/cli/blob/3419a87d6fb620a2ea7981cdd6cd43db3b17cb5f/packaging/deb/dotnet-debian_config.json
Nodes especially important are maintainer_*, maintainer_email, install_root, *_description, homepage, copyright and license.
The package_name and package_version are overridden by the values passed explicitly to the dotnet deb tool. The values in release and control seem to be dummy values though I need to verify them.
The generation of deb installers is ready. I'll split the rpm generation into a different PR since that uses a different tool and requires some more work. |
|
||
<Target Name="BuildRuntimeStoreDeb"> | ||
<PropertyGroup> | ||
<RuntimeStoreTimestampDebianPackageName>aspnetcore-store-$(TimestampVersion)</RuntimeStoreTimestampDebianPackageName> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This follows the CLI naming scheme:
Package name: aspnetcore-store-{version}, in the CLI: https://github.com/dotnet/cli/blob/358568b07f16749108dd33e7fea2f2c84ccf4563/build/package/Installer.DEB.targets#L30
Package file name: aspnetcore-store-{version}-{RID}, in the CLI: https://github.com/dotnet/cli/blob/358568b07f16749108dd33e7fea2f2c84ccf4563/build/Branding.props#L31
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes me question if aspnet/MetaPackages is the right place for this step. At this point, most of the runtime store generation is so dependent on the layout of coherence-signed output, it seems like this should be coherence-final instead.
|
||
<!-- Build Docker Image --> | ||
<Exec | ||
Command="docker build --build-arg USER_ID=%24(id -u) -t docker-image-$(InstallerPlatform) $(InstallerPlatform)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be good to assert that the docker host is using Linux containers, not windows containers.
$ docker version -f "{{ .Server.Os }}"
linux
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assert added.
<Target Name="BuildRuntimeStoreDeb"> | ||
<PropertyGroup> | ||
<RuntimeStoreTimestampDebianPackageName>aspnetcore-store-$(TimestampVersion)</RuntimeStoreTimestampDebianPackageName> | ||
<RuntimeStoreNoTimestampDebianPackageName>aspnetcore-store-$(NoTimestampVersion)</RuntimeStoreNoTimestampDebianPackageName> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have we verified the naming of runtimes-store installers with the PMs? //cc @richlander, cref https://github.com/dotnet/designs/issues/2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm following the convention highlighted by @DamianEdwards in #124 though I'm not sure if this is correct. That's why I called out on it in my previous comment. This needs to be checked by a PM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@glennc, can you signoff on the naming here?
@natemcmaster This actually requires an additional configuation on TeamCity that runs after coherence-signed on a Linux machine. We don't have a coherence-final configuration so I'm just using MetaPackages. |
We can make new configurations if required. It just seems pointless to have this code in aspnet/Metapackages if it depends on the way coherence-signed works as Coherence-signed is private. It would be better to ensure this code works on its own. Context: there is a "build from source" effort currently underway to make it easier for people to build asp/.net core on their own. |
tools/docker/debian/Dockerfile
Outdated
@@ -0,0 +1,51 @@ | |||
# | |||
# Copyright (c) .NET Foundation and contributors. All rights reserved. | |||
# Licensed under the MIT license. See LICENSE file in the project root for full license information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update these to Apache.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm signing off on the license/links in the PR. Don't know the functionality 😄
</PropertyGroup> | ||
|
||
<ItemGroup> | ||
<DotNetCliToolReference Include="Build.RS" Version="$(AspNetCoreVersion)" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you mean PackageReference
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
copy pasta
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Got an offline |
8cfd9ef
to
f8605a4
Compare
f8605a4
to
07a227f
Compare
Addresses #149