From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [ndctl PATCH] rpmbuild: ensure the rpmbuild working directories are present
Date: Mon, 27 Nov 2017 19:04:40 +0000 [thread overview]
Message-ID: <1511809477.16069.1.camel@intel.com> (raw)
In-Reply-To: <CAPcyv4jSc_wyEDUnqjof_1VNmWHn4ZWg3wwMqCv4OV-Ri+MUhQ@mail.gmail.com>
On Wed, 2017-11-22 at 15:49 -0800, Dan Williams wrote:
> On Wed, Nov 22, 2017 at 2:15 PM, Verma, Vishal L
> <vishal.l.verma@intel.com> wrote:
> >
> > On Wed, 2017-11-22 at 14:13 -0800, Dan Williams wrote:
> > > On Wed, Nov 22, 2017 at 2:00 PM, Vishal Verma <vishal.l.verma@int
> > > 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 <dan.j.williams@intel.com>
> > > > Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> > > > ---
> > > > 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
prev parent reply other threads:[~2017-11-27 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 22:00 [ndctl PATCH] rpmbuild: ensure the rpmbuild working directories are present Vishal Verma
2017-11-22 22:13 ` Dan Williams
2017-11-22 22:15 ` Verma, Vishal L
2017-11-22 23:49 ` Dan Williams
2017-11-27 19:04 ` Verma, Vishal L [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1511809477.16069.1.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-nvdimm@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.