Skip to content

packaging: remove legacy .egg references from Makefile.com#429

Open
abubakarsabir924-cell wants to merge 1 commit intoOpenPrinting:masterfrom
abubakarsabir924-cell:remove-legacy-egg-references
Open

packaging: remove legacy .egg references from Makefile.com#429
abubakarsabir924-cell wants to merge 1 commit intoOpenPrinting:masterfrom
abubakarsabir924-cell:remove-legacy-egg-references

Conversation

@abubakarsabir924-cell
Copy link
Copy Markdown

This PR addresses the request by Till Kamppeter to clean up legacy Python packaging references. I have commented out the .egg and egg-info cleanup rules in Makefile.am as they are no longer required for modern build systems.

@abubakarsabir924-cell abubakarsabir924-cell force-pushed the remove-legacy-egg-references branch from 0b3a208 to a97b297 Compare March 26, 2026 19:53
@abubakarsabir924-cell
Copy link
Copy Markdown
Author

Hi @tillkamppeter Sir, I have updated the Pull Request. I've commented out the legacy .egg and egg-info references in Makefile.am as requested. Also, I've cleaned up the indentation to ensure the PR is neat. Please have a look. Thank you

@tillkamppeter
Copy link
Copy Markdown
Member

Can one not just delete these lines instead of commenting them out?

@abubakarsabir924-cell abubakarsabir924-cell force-pushed the remove-legacy-egg-references branch from a97b297 to 820a3f8 Compare March 27, 2026 07:31
@abubakarsabir924-cell
Copy link
Copy Markdown
Author

abubakarsabir924-cell commented Mar 27, 2026

Hi @tillkamppeter ! I have deleted the legacy lines as suggested. To be honest, I was initially cautious and only commented them out because I didn't want to accidentally break anything in such a major organization. I wanted to move step-by-step to ensure total accuracy, as it is my dream to work with you and the OpenPrinting team for GSoC. The PR is now clean and ready for review. Thank you for your guidance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants