From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 6EE0E20359EA7 for ; Mon, 27 Nov 2017 11:00:20 -0800 (PST) From: "Verma, Vishal L" Subject: Re: [ndctl PATCH] rpmbuild: ensure the rpmbuild working directories are present Date: Mon, 27 Nov 2017 19:04:40 +0000 Message-ID: <1511809477.16069.1.camel@intel.com> References: <20171122220019.16041-1-vishal.l.verma@intel.com> <1511388916.3866.26.camel@intel.com> In-Reply-To: Content-Language: en-US Content-ID: MIME-Version: 1.0 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: "Williams, Dan J" Cc: "linux-nvdimm@lists.01.org" List-ID: On Wed, 2017-11-22 at 15:49 -0800, Dan Williams wrote: > On Wed, Nov 22, 2017 at 2:15 PM, Verma, Vishal L > wrote: > > > > On Wed, 2017-11-22 at 14:13 -0800, Dan Williams wrote: > > > On Wed, Nov 22, 2017 at 2:00 PM, Vishal Verma > > el.c > > > om> wrote: > > > > The rpmbuild and make-git-snapshot assume that the various > > > > ~/rpmbuild/* > > > > directories are present. In case they weren't, git-archive > > > > would > > > > fail > > > > with something like: > > > > > > > > /root/rpmbuild/SOURCES/ndctl-58.2.38.g8ad8f4c.tar.gz: No such > > > > file or directory > > > > > > > > Add a 'mkdir -p' to make sure these directories are present. > > > > > > > > Cc: Dan Williams > > > > Signed-off-by: Vishal Verma > > > > --- > > > > rpmbuild.sh | 1 + > > > > 1 file changed, 1 insertion(+) > > > > > > > > diff --git a/rpmbuild.sh b/rpmbuild.sh > > > > index 4535b46..1dd1709 100755 > > > > --- a/rpmbuild.sh > > > > +++ b/rpmbuild.sh > > > > @@ -1,5 +1,6 @@ > > > > #!/bin/bash > > > > pushd $(dirname $0) >/dev/null > > > > +mkdir -p ~/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS} > > > > > > Hmm, I'd rather run rpmdev-setuptree than create this directories > > > manually, and going further I'd rather just keep the assumption > > > that > > > rpmdev-setuptree has already been run before this script is run. > > > > We could do a test -d ~/rpmbuild/SOURCES or so, and if not found, > > then > > run rpmdev-setuptree? > > We know we are about to write to that path, so if it doesn't exist, > > why > > not create it? > > Because we expect to build into an initialized rpmbuild tree, and if > it's not initialized failing seems appropriate. That said, I'm ok > with > your "test and call rpmdev-setuptree" proposal. > > Actually rpmdev-setuptree will overwrite any rpmmacros file, so maybe it is best not to call it and risk changing users environments. I'll send a patch to check for it though, and if not found, print an error message and exit out. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm