This is the mail archive of the libc-ports@sources.redhat.com mailing list for the libc-ports 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]

consistency in glibc add-on directory names?


  what are the chances of standardizing on a naming convention for the
top-level directory names in glibc add-on tarballs?  i'm writing a
script to automate some add-on management and it's kind of annoying
that there are the following top-level names for the add-ons:

  glibc-linuxthreads-2.3.5.tar.bz2 -> linuxthreads
  glibc-libidn-2.3.5.tar.bz2 -> libidn
  glibc-ports-2.3.5.tar.bz2 -> glibc-ports-2.3.5   (argh!)

thoughts?

rday


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