This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 1/3] Import mkdir module
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Doug Evans <dje at google dot com>
- Cc: Yao Qi <yao at codesourcery dot com>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Tue, 19 Mar 2013 13:59:21 -0700
- Subject: Re: [PATCH 1/3] Import mkdir module
- References: <83ip4s4ixc dot fsf at gnu dot org> <1363407692-18959-1-git-send-email-yao at codesourcery dot com> <1363407692-18959-2-git-send-email-yao at codesourcery dot com> <CADPb22Rvf6Ky4N_p8ELQy=wJ=+YN2Yf7qe+Te3H_=cFB45Pk-w at mail dot gmail dot com>
> > 1. Check out my gulib repository to
> > 8d5bd1402003bd0153984b138735adf537d960b0, which is required by
> > update-gnulib.sh, so that we just import mkdir module instead
> > of upgrading gnulib we are using.
> > 2. Modify update-gnulib.sh to add mkdir.
> > 3. bash update-gnulib.sh <my gnulib repository>
> >
> > Build GDB with all-targets enabled and cross compile GDB for mingw32
> > target.
>
> Hi.
> A ton of random stuff got dragged in.
> Is this typical of gnulib?
>
> Including, but not limited to, the following.
>
> If all this extra stuff is just due to updating to a newer version of
> gnulib, please separate out the update from the addition of mkdir.
Looking at the SHA1 and the update procedure, Yao used the correct
version of gnulib, and the extra stuff are dependencies. This is
typical of gnlib, and OK. I see where Eli is coming from when
he proposes implementing it locally rather than dependening on
gnulib, but I do feel like it's better to take advantage of gnulib
for portability issues. So I have a preference for gnulib, but
I will not object to a local implementation instead.
--
Joel