From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mailout-de.gmx.net ([213.165.64.22]) by metis.ext.pengutronix.de with smtp (Exim 4.72) (envelope-from ) id 1RDNmk-0000Hn-UT for ptxdist@pengutronix.de; Mon, 10 Oct 2011 23:53:24 +0200 Message-ID: <4E93694A.2070807@gmx.de> Date: Mon, 10 Oct 2011 23:53:14 +0200 From: Gavin Schenk MIME-Version: 1.0 References: <20111007123518.183940@gmx.net> <201110071508.02537.jbe@pengutronix.de> <4E931DED.6000703@gmx.de> <20111010212110.GJ18273@pengutronix.de> In-Reply-To: <20111010212110.GJ18273@pengutronix.de> Subject: Re: [ptxdist] Makefile in subfolder of rules directory? Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de > On Mon, Oct 10, 2011 at 06:31:41PM +0200, Gavin Schenk wrote: >> Today we reviewed your hints and had a close look to the result of >> ptxdist newpackage src-make-prog, but still have issues with it. >> Maybe my question was too imprecise. >> >> It is possible to put the in-files into subdirectories e.g. >> project/rules/somedir/test.in! >> But in this example the corresponding makefile in >> project/rules/somedir/test.make is not recognized by ptxdist. >> >> It seems to me, that ptxdist only scans project/rules but not any >> subdirs for makefiles. > > Right, and this is by design. > > Why do you want to use a sub directory? The strategy is usually to put > any project-local .in and .make files into rules/. Any file put there > should be generic enough to be used in any config/platform to be used > with the project, so I cannot imagine a good reason for splitting up > into sub directories. > > rsc The only reason is that I want to share the .in and .make files using subversion, by checking out a common rules-folder as external into the project. Changes to this external are visible to all colleagues immediately, the external can be sticked to a version, switched to trunk, tag, branch or whatever one need. My solution is to check out the common_rules beside the projects rules-folder and copy the common_rules content, using lndir, into the rules-folder. That meets all requirements, I only have to update the symbolic links after an update from subversion. Thanks and Regards, Gavin -- ptxdist mailing list ptxdist@pengutronix.de