On 11/16/2016 6:54 AM, Jeff Epler wrote: > On Wed, Nov 16, 2016 at 06:13:35AM -0600, Jim Craig wrote: >> If I develop this application around the python-pygoocanvas package can >> we modify the standard linuxcnc distribution to include this package by >> default? If so I will continue and modify the code to use this new >> canvas for the drawing portion of the application. > In Debian packaging, the requirements of each package are listed (lists > of more Debian package names) in the package metadata. > > So in the end, when your application is packaged as a Debian package, > installing it will automatically install the dependencies. > > This doesn't require changing "the standard linuxcnc distribution" to > list python-pygoocanvas somewhere, except in the dependency list of the > hypothetical new package (and then installing the package itself) > > Jeff > > ------------------------------------------------------------------------------ > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers > Jeff,
Thanks for the info. I was not quite sure how the roll out of my application would actually take place. So what you are saying is that I will make a deb for my application and then if the linuxcnc project accepts this application as part of the overall linuxcnc project then my deb will be included in the overall install for linuxcnc via deb or via live image? I am new to this type of project. All of my previous programming has been for in house corporate applications that are not distributed to the general public. I have never worked on a large collaborative project like this. Thanks, Jim ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
