Re: [ANNOUNCEMENT] Updated: suite3270-3.3.4p7-1, c3270-3.3.4p7-1, pr3287-3.3.4p7-1, s3270-3.3.4p7-1, tcl3270-3.3.4p7-1, x3270-3.3.4p7-1

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCEMENT] Updated: suite3270-3.3.4p7-1, c3270-3.3.4p7-1, pr3287-3.3.4p7-1, s3270-3.3.4p7-1, tcl3270-3.3.4p7-1, x3270-3.3.4p7-1

Eric Blake-2
>
> NOTE: The previous release of suite3270 for Cygwin incorrectly named the
> pr3287 package as 'pr3270'.  This release corrects the package name.  The
> previous, incorrectly, named package will remain until that release
> (3.2.20) is removed from the distribution sometime in the future.

For the package rename to work, you should provide an empty tarball named
suite3270/pr3270/pr3270-3.3.4p7-1.tar.bz2, then update that setup.hint
to require: the pr3287 package and mark suite3270 in the _obsolete
category.  Otherwise, people might be stuck with the old pr3270 package,
possible with version mismatch problems, because setup.exe didn't
auto-update to pull in the new package name.

--
Eric Blake
Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCEMENT] Updated: suite3270-3.3.4p7-1, c3270-3.3.4p7-1, pr3287-3.3.4p7-1, s3270-3.3.4p7-1, tcl3270-3.3.4p7-1, x3270-3.3.4p7-1

Peter A. Castro
On Thu, 9 Feb 2006, Eric Blake wrote:

>> NOTE: The previous release of suite3270 for Cygwin incorrectly named the
>> pr3287 package as 'pr3270'.  This release corrects the package name.  The
>> previous, incorrectly, named package will remain until that release
>> (3.2.20) is removed from the distribution sometime in the future.
>
> For the package rename to work, you should provide an empty tarball named
> suite3270/pr3270/pr3270-3.3.4p7-1.tar.bz2, then update that setup.hint
> to require: the pr3287 package and mark suite3270 in the _obsolete
> category.  Otherwise, people might be stuck with the old pr3270 package,
> possible with version mismatch problems, because setup.exe didn't
> auto-update to pull in the new package name.

No, this won't work.  There's only one setup.hint per package and it's
not versionable (at least not that I can find).  Besides, suite3270 is a
base package and the other packages (eg: c3270, pr3287, etc) require *it*
and not the other way around.  I went a few rounds with Chris and Corinna
on package organization in the beginning for these and it was decided
that the current organization is the best, and I'm not changing it.

At present, there are two packages in the list: pr3270 and pr3287.
Eventually pr3270 will be obsoleted and removed and anyone who needs the
latest version will simply have to pick it up by the correct name.  It's
not that big a deal.  Heck, in the world of Linux packages it seems most
packages of a given distribution change names each major release (well,
at least that's how it appears to me :)

And, honestly, pr3287 is a lesser know/used package.  Anyone who really
needs it will know to look for the correct name in the future.

> --
> Eric Blake

--
Peter A. Castro <[hidden email]> or <[hidden email]>
  "Cats are just autistic Dogs" -- Dr. Tony Attwood
Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCEMENT] Updated: suite3270-3.3.4p7-1, c3270-3.3.4p7-1, pr3287-3.3.4p7-1, s3270-3.3.4p7-1, tcl3270-3.3.4p7-1, x3270-3.3.4p7-1

Igor Peshansky
On Wed, 8 Feb 2006, Peter A. Castro wrote:

> On Thu, 9 Feb 2006, Eric Blake wrote:
>
> > > NOTE: The previous release of suite3270 for Cygwin incorrectly named
> > > the pr3287 package as 'pr3270'.  This release corrects the package
> > > name.  The previous, incorrectly, named package will remain until
> > > that release (3.2.20) is removed from the distribution sometime in
> > > the future.
> >
> > For the package rename to work, you should provide an empty tarball
> > named suite3270/pr3270/pr3270-3.3.4p7-1.tar.bz2, then update that
> > setup.hint to require: the pr3287 package and mark suite3270 in the
> > _obsolete category.  Otherwise, people might be stuck with the old
> > pr3270 package, possible with version mismatch problems, because
> > setup.exe didn't auto-update to pull in the new package name.
>
> No, this won't work.  There's only one setup.hint per package and it's
> not versionable (at least not that I can find).  Besides, suite3270 is a
> base package and the other packages (eg: c3270, pr3287, etc) require
> *it* and not the other way around.  I went a few rounds with Chris and
> Corinna on package organization in the beginning for these and it was
> decided that the current organization is the best, and I'm not changing
> it.

I think Eric misread your message as having *all* the names changed to
*3287 from *3270.  His point is still valid, though -- since this is a
rename, and (I assume) the content overlaps, the pr3270 package (which has
a separate setup.hint) should be marked _obsolete and should require: the
pr3287 package (to allow seamless updates for people who used to have
pr3270 installed).

> At present, there are two packages in the list: pr3270 and pr3287.
> Eventually pr3270 will be obsoleted and removed and anyone who needs the
> latest version will simply have to pick it up by the correct name.
> It's not that big a deal.  Heck, in the world of Linux packages it seems
> most packages of a given distribution change names each major release
> (well, at least that's how it appears to me :)

The problem is that, unless you pr3270 is obsoleted, its content would
clash with pr3287.  When people later uninstall the old pr3270 package,
the files that belong to pr3287 will be removed, so pr3287 will have to be
reinstalled.

> And, honestly, pr3287 is a lesser know/used package.  Anyone who really
> needs it will know to look for the correct name in the future.

Why not just let setup do it automatically?  That way you prevent the
obvious issues people (even those few that use the package) will
undoubtedly have on an upgrade.
HTH,
        Igor
--
                                http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_    [hidden email] | [hidden email]
ZZZzz /,`.-'`'    -.  ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-' old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCEMENT] Updated: suite3270-3.3.4p7-1, c3270-3.3.4p7-1, pr3287-3.3.4p7-1, s3270-3.3.4p7-1, tcl3270-3.3.4p7-1, x3270-3.3.4p7-1

Peter A. Castro
On Thu, 9 Feb 2006, Igor Peshansky wrote:

> On Wed, 8 Feb 2006, Peter A. Castro wrote:
>> On Thu, 9 Feb 2006, Eric Blake wrote:
>>
>>>> NOTE: The previous release of suite3270 for Cygwin incorrectly named
>>>> the pr3287 package as 'pr3270'.  This release corrects the package
>>>> name.  The previous, incorrectly, named package will remain until
>>>> that release (3.2.20) is removed from the distribution sometime in
>>>> the future.
>>>
>>> For the package rename to work, you should provide an empty tarball
>>> named suite3270/pr3270/pr3270-3.3.4p7-1.tar.bz2, then update that
>>> setup.hint to require: the pr3287 package and mark suite3270 in the
>>> _obsolete category.  Otherwise, people might be stuck with the old
>>> pr3270 package, possible with version mismatch problems, because
>>> setup.exe didn't auto-update to pull in the new package name.
>>
>> No, this won't work.  There's only one setup.hint per package and it's
>> not versionable (at least not that I can find).  Besides, suite3270 is a
>> base package and the other packages (eg: c3270, pr3287, etc) require
>> *it* and not the other way around.  I went a few rounds with Chris and
>> Corinna on package organization in the beginning for these and it was
>> decided that the current organization is the best, and I'm not changing
>> it.
>
> I think Eric misread your message as having *all* the names changed to
> *3287 from *3270.  His point is still valid, though -- since this is a
> rename, and (I assume) the content overlaps, the pr3270 package (which has
> a separate setup.hint) should be marked _obsolete and should require: the
> pr3287 package (to allow seamless updates for people who used to have
> pr3270 installed).

Ah, I see now.  Yes, that does sound like a good idea.

Eric, sorry I misunderstood what your were trying to say. :)

Ok, I'll do that tonight and it should hit the mirrors there after.
Umm... do I need to do another announcement for this?

>> At present, there are two packages in the list: pr3270 and pr3287.
>> Eventually pr3270 will be obsoleted and removed and anyone who needs the
>> latest version will simply have to pick it up by the correct name.
>> It's not that big a deal.  Heck, in the world of Linux packages it seems
>> most packages of a given distribution change names each major release
>> (well, at least that's how it appears to me :)
>
> The problem is that, unless you pr3270 is obsoleted, its content would
> clash with pr3287.  When people later uninstall the old pr3270 package,
> the files that belong to pr3287 will be removed, so pr3287 will have to be
> reinstalled.
>
>> And, honestly, pr3287 is a lesser know/used package.  Anyone who really
>> needs it will know to look for the correct name in the future.
>
> Why not just let setup do it automatically?  That way you prevent the
> obvious issues people (even those few that use the package) will
> undoubtedly have on an upgrade.

Yes, I quite agree.  I'll go about correcting this tonight.
Thanks again!

> HTH,
> Igor

--
Peter A. Castro <[hidden email]> or <[hidden email]>
  "Cats are just autistic Dogs" -- Dr. Tony Attwood
Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCEMENT] Updated: suite3270-3.3.4p7-1, c3270-3.3.4p7-1, pr3287-3.3.4p7-1, s3270-3.3.4p7-1, tcl3270-3.3.4p7-1, x3270-3.3.4p7-1

Igor Peshansky
On Thu, 9 Feb 2006, Peter A. Castro wrote:

> On Thu, 9 Feb 2006, Igor Peshansky wrote:
>
> > On Wed, 8 Feb 2006, Peter A. Castro wrote:
> > > On Thu, 9 Feb 2006, Eric Blake wrote:
> > >
> > > > > NOTE: The previous release of suite3270 for Cygwin incorrectly
> > > > > named the pr3287 package as 'pr3270'.  This release corrects the
> > > > > package name.  The previous, incorrectly, named package will
> > > > > remain until that release (3.2.20) is removed from the
> > > > > distribution sometime in the future.
> > > >
> > > > For the package rename to work, you should provide an empty
> > > > tarball named suite3270/pr3270/pr3270-3.3.4p7-1.tar.bz2, then
> > > > update that setup.hint to require: the pr3287 package and mark
> > > > suite3270 in the _obsolete category.  Otherwise, people might be
> > > > stuck with the old pr3270 package, possible with version mismatch
> > > > problems, because setup.exe didn't auto-update to pull in the new
> > > > package name.
> > >
> > > No, this won't work.  There's only one setup.hint per package and
> > > it's not versionable (at least not that I can find).  Besides,
> > > suite3270 is a base package and the other packages (eg: c3270,
> > > pr3287, etc) require *it* and not the other way around.  I went a
> > > few rounds with Chris and Corinna on package organization in the
> > > beginning for these and it was decided that the current organization
> > > is the best, and I'm not changing it.
> >
> > I think Eric misread your message as having *all* the names changed to
> > *3287 from *3270.  His point is still valid, though -- since this is a
> > rename, and (I assume) the content overlaps, the pr3270 package (which
> > has a separate setup.hint) should be marked _obsolete and should
> > require: the pr3287 package (to allow seamless updates for people who
> > used to have pr3270 installed).
>
> Ah, I see now.  Yes, that does sound like a good idea.
>
> Eric, sorry I misunderstood what your were trying to say. :)
>
> Ok, I'll do that tonight and it should hit the mirrors there after.
> Umm... do I need to do another announcement for this?

Probably not.  Since the only changes are to the setup.hint files, you
won't even need to bump the Cygwin release number.  You might want to send
out a separate note saying that pr3270 was superseded by pr3287, though...
        Igor
--
                                http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_    [hidden email] | [hidden email]
ZZZzz /,`.-'`'    -.  ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-' old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"