Found these details

I just ran into these two page which seems quite practical for building openerp/odoo

http://pythonhosted.org/anybox.recipe.openerp/ 

https://pypi.python.org/pypi/anybox.recipe.odoo

They could be helpful in building TKLDEV image.

Thanks for your help.  I will review in detail.

I am not always clear but I do try to parse outlines from threads.  I will look in detail at your http://www.turnkeylinux.org/docs/tkldev-new-appliance instructions  (expect I was there before).

I have to look at the LAPP plan again, but I do recall it's calling itself  (that perplexed me)... In Lapp/ Plan/Main it was calling right from the start ...   (you are right, it is not in conf.d).  

So on to my objective?

Did you build a Fork of Lapp for Odoo?  Will see if I can find one.  I'm on the fence between Apache and NGINX for Odoo.  I have seen recent call outs for Apache but most have been for NGINX.  Apache I can navigate so that pulls me that way.  So far my Odoo homebrew is in Postgresql App, so I am comparing different App builds to see how they come together.

In my last round on this a few weeks ago I was basically setting up a horse-race.  Three approaches were modifying the Postgresql, the LAPP, or the Tendenci appliance to build Odoo.   Doing so they had very different structures though and I was therefore trying to understand the sequencing system of TKLDEV. 

Less chat, more do.  I will read more on all this.

ISSUE SOLVED via COMMENT BELOW this ENTRY

to see how I got there read on

Yesterday:  I Cloned Lapp, renamed to Odoo-lapp.  Briefly changed the line

include $(FAB_PATH)/common/mk/turnkey/lapp.mk

to:

include $(FAB_PATH)/common/mk/turnkey/odoo-lapp.mk

(Changed it back shortly thereafter but after my Pull to the Turnkey Directory.  When I repulled to the Root version directory I verified the change and assumed all was good.  It was not.  This caused my error in that I changed it back but did not pull to the correct directory as was following 2 sets of instructions and had 2 sets of code in TKLDEV)

Today:

ran tkldev-setup

 Ran Make

Error Reads:

Makefile:4: /turnkey/fab/common/mk/turnkey/odoo-lapp.mk:  No such file or directory

make: *** No rule to make target '/turnkey/fab/common/mk/turnkey/odoo-lapp.mk".

Stop

----------

It noticed after TKLDEV-SETUP that a Core folder had been brought in.  I did not Clone it myself.

Changed to Folder Core (from odoo-lapp which is parrallel)

Ran MAKE on CORE:  ran successfully.

------------

Since My Odoo-Lapp does not install however (cloned, renamed but otherwise unchanged LAPP) ???

Perhaps since I changed the name of Lapp to Odoo-Lapp perhaps I need to help new folders withthat name be created that are not crated by the General Make Process.

If I had this still be Lapp, would it run by itself?

I am missing something.

-----------

Postscripts Below 

-----------

1:  potential issue: proceeding but  can I not run this from a OVF Built system?  You reference OVZ problems here:

http://www.turnkeylinux.org/forum/support/20140824/trying-install-minecraft-turnkey-server

that Core make is working it would seem the system is operating so red flag.

-----------------

2: TKLDEV-SETUP:  Yesterday at TKLDEV installation, this didn't jump out of the blog instructions I was following in the blog post (Docs are good) but

https://github.com/turnkeylinux-apps/tkldev/blob/master/docs/setup.rst

./tkldev-setup

B. Setup the build dependencies

In the next version of TKLDev, you can skip this step because it happens automatically on first boot.

If it doesn't (e.g., we didn't have a working Internet connection) you'll be able to trigger it by running this command inside TKLDev as root:

But you're not using the next version of TKLDev (yet), so you'll want to download the new tkldev-setup from GitHub:

cd /usr/local/sbin
wget https://raw.githubusercontent.com/turnkeylinux-apps/tkldev/master/overlay/usr/local/sbin/tkldev-setup
chmod +x tkldev-setup

./tkldev-setup

Do the "Manual Installs" also need to be done after /tkldev-setup ?  They appear to have been built w/ tkldev-setup

The build dependencies: what are they?

1. bootstrap in /turnkey/fab/bootstraps: contains minimal bootstrap filesystems.
2. cdroots in /turnkey/fab/cdroots: contains the cdroot template for the built ISO.
3. common in /turnkey/fab/common: contains source code shared amongst all TurnKey systems.

It appears this was all built in TKL-Dev-setup command

That Core built it would appear all is OK for the system.  

I will look at Pulling Lapp in by itself and seeing if it will Make by itself.  Then it will for sure be something w/ the Name Change I gave yesterday, from your docs/blog post:

---------------------

(My PROBLEM was not navigating to /turnkey/fab/products/new-app-name folder before running these commands.  Therefore dropped separate file set into Root/new-app-name

However, I also followed the GitHub docs and did pull the folder there - just had a test error in the MakeFile which is explained in the comment below)

git clone https://github.com/turnkeylinux-apps/<base-appliance-name>.git
mv <base-appliance-name> <new-appliance-name>
cd <new-appliance-name>
rm -rf .git
git-init

I just organized all my Browser Tabs on the Current Subject.  Have not really started changing the App yet, but to get to Here (2 Makes, one for Core, one for Lapp)  I have 25 Tabs OPEN. (will start closing)

One difficulty I see is that often instructions refer to other instructions and, in the short rabbit run just now, one or two small details got left off the follower's (my) outline.

Important details are mostly in the TKLDEV-GitHub Docs, but trying to follow the TKLDOC/Blog entry is attractive because Several pages are condensed to one.

Now my notation needs to be updated to be sure today's Tkldev-setup and be sure the Folder path is in Turnkey/fab/products.

Excited to start building the APP now.

Assuming that LAPP will be modified in the future and that at present we are discussing a "copy" of LAPP as today, would it not make sense to have a completely Bare system which simply includes whatever is in the current version of LAPP, and then goes on to modify it?

 I can see that the TurnkeyLinux-apps/lapp is indeed quite Bare (and including the Base and Lapp plan in 

https://github.com/turnkeylinux/common/tree/master/plans/turnkey

----------

But I can see that many Apps do not have a Plan under the common tree.  Lets take Magento for a moment.  Lets say I wanted a Magento App that is based upon Magento but which has significant changes.  I would want to take ongoing changes to the Magento App, but I would also want to have 3 other downloads go in, and when the version changes, the general capability of the system would change.  Moreover, if there were major changes to the Magento-App those would be automatically pulled and integrated to the changes I wanted to have.

Esoteric process question perhaps.

https://github.com/turnkeylinux-apps/tkldev/blob/master/docs/tips.rst

Brings some clarity to this.

(Reference of following comand I want to understand more.

make clean && Make

Likewise.  What would be the command to rerun Make but not Install any Packages OR Downloads?

(I.E.  I am just working on the config files coordinating correctly)

Hopefully my learning is shareable.

Really like what a I have been able to build.  Will ask other questions separately.  Simple is the kay.  

One last ?  If I change one .conf or .php file on GitHub, then run git pull..  do I have to run make clean, or can it just be make?

I would love to see some git and package repositories that can be declared as "built" so that so much time is not burned pulling both.  Make will use pre pulled packages especially helpful with abtimeout failure.  It does not work with Git.  I am not sure what happens with small files. Perhaps they integrated in subsequent makes?

I will work on understanding and testing your last comment jeremy.  Likely a trove of info that just needs to be digested with some practice.

Do it well and the issues go away.

Thanks to all.