This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Fix in-src-tree builds by making gdbserver/gnulib/ a separate library (a la libiberty, etc.), and adding ACX_CONFIGURE_DIR.


On 04/18/2012 12:25 AM, Joel Brobecker wrote:

>> Okay, then here's the current list, adding "gnulib-wrap", for
>> being shorter than "wrapper", while meaning basically the same.
>>
>>    gnulib-wrap/gnulib/
>>    gnulib-wrapper/gnulib/
>>    gnulib-pkg/gnulib/
>>
>> I'm torn now between gnulib-wrap and gnulib-pkg, pending
>> more towards wrap.  I think I'll go with that if I don't hear other
>> preferences, but any of those is fine with me.  Anyone?
> 
> gnulib-glue? (hmm, not great, as it's more than glue, but we can
>               twist the meaning of glue to include the import)

> gnulib-import? (to me, the extra characters are not an issue)

I dislike gnulib-import as with gnulib-import/gnulib, the import
is really on the "gnulib" subdir, and the "gnulib-import" is about
the autoconf wrapping that is _not_ imported, so it feels
backwards to me.

> Personally, my preference is gnulib/gnulib, and I remember seeing
> plenty of packages follow that pattern, so I don't feel that there
> is anything wrong with this. 


Oh, shucks.  Glad I haven't done any renaming yet.  :-)
That's two votes for plain "gnulib/gnulib", one against.

> But on the other hand, it's not very
> important, so whatever gets decided is fine by me (even gnulib-wrap,
> which unfortunately is my least favorite :-P).


Clearly we'll not be able to make everybody happy.
I understood Jan's comment as a suggestion, not an objection, so
I'll take the path of least effort, and get this over with.

-- 
Pedro Alves


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]