Skip to content

Packaging for new autogen-* 0.4 packages does not include license files #3673

@jackgerrits

Description

@jackgerrits

What happened?

The built packages do not contain LICENSE or LICENSE-CODE in them like the existing package does. However, it is at least correctly tagged based on the classifiers

What did you expect to happen?

LICENSE and LICENSE-CODE should be included and License-Expression should be set on the metadata.

Because the packaging requires the license file to be in the source tree I see two options:

  1. We include these files in the source tree for each package
  2. We copy the files to the right location prior to building

While 1 introduces more files into the repo and is a bit noisy I think it is the better solution as 2 would break the from VCS install for pip

How can we reproduce it (as minimally and precisely as possible)?

uv build to see packaged files

AutoGen version

staging

Which package was this bug in

Other

Model used

No response

Python version

No response

Operating system

No response

Any additional info you think would be helpful for fixing this bug

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions