[Nfd-dev] Notice about library renaming

[Alex Afanasyev]

On Apr 18, 2014, at 1:34 PM, Burke, Jeff <jburke at remap.ucla.edu> wrote:

> 
> Alex,
> 
> As I've previously mentioned "OpenNDN" isn't particularly descriptive of
> the library, and I think is going to lead to a lot of confusion outside.
> (It doesn't fix the confusion that arose from calling it ndn-cpp-dev.)
> 
> It also seems to set up two parallel library efforts without
> distinguishing between the goals.  What are the goals of OpenNDN?  What
> makes it Open?  Is the other library Closed?  etc. etc.
> 
> I'm really sorry that I haven't been able to make another constructive
> suggestion over the course of this week but I would really like to advise
> against rushing this change.
> 
> One thought: 
> 
> This library was forked originally to support NFD.  Why not rename it to
> libnfd, which is descriptive of what it actually does right now?  This
> will need to stay somewhat stable in support of NFD/NRD development,
> security library work, etc.

Just a quick comment before others comment.

I have never thought of this fork to be of specifically to support NFD.  I will not agree on having nfd in the name, as it is not the distinction or the difference.

---
Alex

> Then, create a separate fork of libnfd with a more general name that
> relates to the approach/intent of the library.  If the approach / intent
> is not clear, then perhaps a little time should be dedicated to deciding
> what the purpose / vision for this particular codebase is?
> 
> cheers,
> Jeff
> 
> 
> 
> On 4/18/14, 1:28 PM, "Alex Afanasyev" <alexander.afanasyev at ucla.edu> wrote:
> 
>> Hi everybody,
>> 
>> Some of you already aware that we are planning to rename ndn-cpp-dev
>> library.  If there are no objections within 24hours, I will proceed with
>> the renaming.   Here is the plan:
>> 
>> * new name: "OpenNDN"
>> * folder name for include files: open-ndn
>> * static library name: libOpenNDN.a
>> * dynamic library name (when it will be enabled): libOpenNDN.so|dylib
>> * pkg-config name: libOpenNDN.pc
>> * no namespace change: we will still use "ndn" as a basic namespace for
>> the library
>> * official github repository will change to:
>> https://github.com/named-data/OpenNDN
>> * redmine will change to http://redmine.named-data.net/projects/openndn
>> * gerrit project name will be changed to OpenNDN
>> (http://gerrit.named-data.net/#/admin/projects/OpenNDN)
>> 
>> We will try to do the change with a transition period, when existing
>> application will still be able to compile against OpenNDN (there will be
>> additional symlinks created for include, lib, and pkg-config files), but
>> all known applications needs to be updated ASAP after the renaming is
>> complete in the following way:
>> 
>> * all includes should be changed from <ndn-cpp-dev/...> to <open-ndn/...>
>> * documentation files/comments referring to ndn-cpp-dev should be updated
>> and refer to OpenNDN and (if any) new links
>> * if the app uses pkg-config for dependency detection, 'libndn-cpp-dev'
>> should be replaced with 'libOpenNDN'.  For waf users:
>> 
>>   conf.check_cfg(package = 'libOpenNDN', args = ['--cflags', '--libs'],
>>                  uselib_store = 'OPEN_NDN', mandatory = True)
>> 
>> (If updating `uselib_store` variable, don't forget to update all uses of
>> it in bld() blocks.)
>> 
>> 
>> I will put this note into the library documentation after the rename.
>> 
>> ---
>> Alex
>> _______________________________________________
>> Nfd-dev mailing list
>> Nfd-dev at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>