Intro paras for Freezing and Packaging your code#548
Intro paras for Freezing and Packaging your code#548kennethreitz merged 9 commits intorealpython:masterfrom
Conversation
I've tried to describe why you would choose one method over another, and what the relative advantages and disadvantages are of each method. I'm painfully aware that I haven't covered the combo of freezing an application *then* creating a Linux distro package of it, but maybe that's a battle for another day. My intent is to add more content on the Freezing page once this commit is accepted, so I can hear your feedback before doing any further work. Thanks.
docs/shipping/freezing.rst
Outdated
There was a problem hiding this comment.
Personally I use 'Mb', but I'm very happy to use MB if that's preferred.
There was a problem hiding this comment.
Yep, fair enough, Wikipedia agrees with you. Commit incoming...
|
I guess with hindsight, I've not remotely made it clear that packaging is pretty much a prerequisite for both freezing and creating a .deb/rpm. I'm also unhappy about not explaining that you might choose to package, and then optionally freeze, and then create a .deb/rpm from that. Personally I think we should merge this PR, then address those issues separately. But I could understand if you feel we should fix the overall structural issues before merging in great wads of text. Let me know and I'd be happy to close this PR without merging, and try again. |
|
Is there a less ambiguous term I should use for .deb/rpm files other than "Linux distribution package"? I don't like the overloaded meanings of "package". |
docs/shipping/freezing.rst
Outdated
Intro paras for Freezing and Packaging your code
|
many thanks! |
4 participants
I've tried to describe why you would choose freezing versus packaging versus creating a Linux distribution package, and the relative advantages and disadvantages of each method.
My intent is to add more content on the Freezing page once this commit is accepted, so I can hear your feedback before doing any further work.