There is 2 directories when you work with buildout: eggs and parts. Also there are declarations of eggs and parts in buildout.cfg. What is purpose of those elements of buildout system?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
There is 2 directories when you work with buildout: eggs and parts. Also there are declarations of eggs and parts in buildout.cfg. What is purpose of those elements of buildout system?
Very simple:
Parts are the building blocks of your buildout. Different parts run different tasks, based on the recipe that is declared for them and the settings configured in that part.
The
partssubdirectory hold the bookkeeping information for each part. It depends on the recipe what is stored here. A CMMI recipe might install the result of the config/make/make install cycle here, for example.Eggs are python package distributions. Buildout uses code from eggs to provide recipe implementations, and most buildouts specify eggs for parts to use in the applications and scripts being built.
It is perfectly legal to have a buildout that doesn’t build anything that uses eggs itself. But for buildout to run the parts, eggs are going to be involved, under the hood.
The
eggssubdirectory usually holds the eggs used for both recipes and anything that requires eggs to run.