libgse team mailing list archive

[Audric Schiltknecht <1045225@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

There is a little inconsistency in naming of the release tarball.
Indeed, the LP project is named 'libgse', and all generated Debian packages 'libgse_XXX.deb'.
However, the tarball is named 'gse-1.0.1.tar.gz', and contains a source directory 'gse-1.0.1'.

For better consistency, releases should be named the same as the
project, that's to say 'libgse'.

** Affects: libgse
     Importance: Undecided
         Status: New

** Affects: libgse/1.0.x
     Importance: Undecided
         Status: New

** Affects: libgse/trunk
     Importance: Undecided
         Status: New

** Also affects: libgse/1.0.x
   Importance: Undecided
       Status: New

** Also affects: libgse/trunk
   Importance: Undecided
       Status: New

** Changed in: libgse/1.0.x
    Milestone: None => 1.0.2

** Changed in: libgse/trunk
    Milestone: None => 1.1.0

-- 
You received this bug notification because you are a member of GSE,
which is subscribed to libgse.
https://bugs.launchpad.net/bugs/1045225

Title:
  Inconsistency in naming

Status in GSE (Generic Stream Encapsulation) library:
  New
Status in libgse 1.0.x series:
  New
Status in libgse trunk series:
  New

Bug description:
  There is a little inconsistency in naming of the release tarball.
  Indeed, the LP project is named 'libgse', and all generated Debian packages 'libgse_XXX.deb'.
  However, the tarball is named 'gse-1.0.1.tar.gz', and contains a source directory 'gse-1.0.1'.

  For better consistency, releases should be named the same as the
  project, that's to say 'libgse'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgse/+bug/1045225/+subscriptions