openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #14031
Re: best practices for merging common into specific projects
-----openstack-bounces+chrisfer=us.ibm.com@xxxxxxxxxxxxxxxxxxx wrote: -----
>To: "andrewbogott@xxxxxxxxx" <andrewbogott@xxxxxxxxx>, Andrew Bogott
><abogott@xxxxxxxxxxxxx>, openstack <openstack@xxxxxxxxxxxxxxxxxxx>
>From: Joshua Harlow
>Sent by: openstack-bounces+chrisfer=us.ibm.com@xxxxxxxxxxxxxxxxxxx
>Date: 07/02/2012 07:21PM
>Subject: Re: [Openstack] best practices for merging common into
>specific projects
>
>
>
>Re: [Openstack] best practices for merging common into specific
>projects
>
>
>What about using openstack-common as a library instead of a
>preprocessor ‘inclusion’ system/copy code around system....??
>
>
>
>Maybe its time for that to happen?
>
>
>
>It always seemed sort of silly to me that files are being copied around
>to different projects like this, instead of referring to code in a
>common library package.
+1
Cheers,
Christopher Ferris
IBM Distinguished Engineer, CTO Industry and Cloud Standards
Member, IBM Academy of Technology
IBM Software Group, Standards Strategy
email: chrisfer@xxxxxxxxxx
Twitter: christo4ferris
phone: +1 508 234 2986
References