public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Kohlsmith <akohlsmith-bluez@benshaw.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] need old bluez-libs and bluez-utils
Date: Sun, 27 Aug 2006 11:50:52 -0400	[thread overview]
Message-ID: <200608271150.52362.akohlsmith-bluez@benshaw.com> (raw)
In-Reply-To: <1156687886.5613.3.camel@aeonflux.holtmann.net>

On Sunday 27 August 2006 10:11, Marcel Holtmann wrote:
> come on. I is actually not that hard to get the latest bluez-utils-2.x
> release. If you don't know how to get them, then you might should not
> get them at all. I am not going to announce old versions. They are

If you do not know the exact point-release then yes, it's a pain in the ass to 
get the older version.  The latest release at the time I was messing around 
with it was 3.2.  The release before was 2.25.  Without googling or going 
through the archives to see what the rev before was, it is a pain in the ass.

Honestly, Marcel... we're not asking you to "announce" old releases, simply 
give access to an indexed HTML or FTP directory so we can grab old versions 
as needed.  May I ask why this is such a problem for you?  Do you presume 
that the latest is always superior to the older releases and once something 
new is released nobody would ever want an older release?

> available, but not linked. I am not fixing stuff in old versions and so
> there is no reason for linking them. People should us and test the
> latest version.

I do understand that you're not fixing older versions, but you are adding more 
and more "weight" to the BlueZ stack... dbus in particular.  I intend to get 
the dbus stuff working on my particular cross-compilation environment, but to 
get it working right now I needed an older version.  You make it difficult to 
get older versions in some mistaken attempt to gain more testers, but all 
you're doing is alienating users who have the wherewithal to help.

-A.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-08-27 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-26 10:50 [Bluez-users] need old bluez-libs and bluez-utils CIJOML
2006-08-26 19:36 ` Andrew Kohlsmith
2006-08-27 14:11   ` Marcel Holtmann
2006-08-27 15:50     ` Andrew Kohlsmith [this message]
2006-08-27 20:38       ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200608271150.52362.akohlsmith-bluez@benshaw.com \
    --to=akohlsmith-bluez@benshaw.com \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox