All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: what to do with wrong checksum
Date: Sun, 8 Nov 2009 15:43:26 +0100	[thread overview]
Message-ID: <ac9c93b10911080643s1ac602a9t3ecc0283da45f6b4@mail.gmail.com> (raw)
In-Reply-To: <hd6k2l$7lv$1@ger.gmane.org>

2009/11/8 Koen Kooi <k.kooi@student.utwente.nl>:
> On 08-11-09 15:08, Frans Meulenbroeks wrote:
>>
>> Without making a comment on the commit message:
>>
>> As stated before the 3.33 version is clearly mentioned as "latest
>> development version" on http://xmltwig.com/xmltwig/
>> The last stable version is 3.32
>> This project decided to provide snapshots (or whatever you want to
>> call it) of the new version. In this case 3.33. Their choice.
>
> 3.33 is a version. A version is a point, not a distance. If it's a snapshot
> than you should call is twig-snapshot, twig-3.33rc1 or whatever.
> Replacing a versioned tarball weekly is *bad*, since you (as upstream
> maintainer) don't know what the "3.33" is your users are complaining about.
> And note that *nowhere* on that page it is stated that the development
> version keeps getting updated. And for that matter it also doesn't say 3.32
> is any better.

Note that I am only relaying what the dev told me and that it by no
means reflect my personal opinion.

And indeed they do not mention that the unstable version can change,
nor that the stable won't change.
It might be that cpan has some rules for not updating stable versions
so it might be that pulling from cpan is better. I don't know cpan and
its way of working well enough to make a statement about that.

--- My personal $ 0.02:
If I want to reuse something from the web, I'm happy that I can get
it, as it saves me work.
If it is not fully the way I want it, I try to convince or educate
them to do things differently.
If they won't, either I have to live with it or avoid that specific
piece of software.
Making snide remarks in a public area only creates irritation and
frustration and does not help./
--- End of my $ 0.02 (and someday I'll learn how to insert a euro
symbol in my emails :-) )

Frans.



  reply	other threads:[~2009-11-08 14:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 20:38 what to do with wrong checksum Frans Meulenbroeks
2009-11-07  3:06 ` Holger Hans Peter Freyther
2009-11-07  8:45   ` Philip Balister
2009-11-07  9:06   ` Frans Meulenbroeks
2009-11-07  9:10     ` Holger Hans Peter Freyther
2009-11-07  9:39       ` Frans Meulenbroeks
2009-11-07 13:23     ` Mike Westerhof
2009-11-07 13:50       ` Holger Hans Peter Freyther
2009-11-07 14:42       ` Koen Kooi
2009-11-07 16:38         ` Otavio Salvador
2009-11-07 18:00           ` Frans Meulenbroeks
2009-11-07 19:01             ` Otavio Salvador
2009-11-07 20:14               ` Frans Meulenbroeks
2009-11-07 14:41 ` Koen Kooi
2009-11-07 22:02 ` Koen Kooi
2009-11-07 22:11   ` Otavio Salvador
2009-11-08 12:23   ` Michael 'Mickey' Lauer
2009-11-08 13:19     ` Koen Kooi
2009-11-08 14:08       ` Frans Meulenbroeks
2009-11-08 14:20         ` Koen Kooi
2009-11-08 14:43           ` Frans Meulenbroeks [this message]
2009-11-08 14:59           ` Otavio Salvador
2009-11-08 14:55         ` Otavio Salvador
2009-11-08 15:40           ` Koen Kooi
2009-11-08 21:31             ` Graham Gower
2009-11-08 22:26               ` Przemyslaw Wesolek
2009-11-08 14:09       ` Philip Balister

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=ac9c93b10911080643s1ac602a9t3ecc0283da45f6b4@mail.gmail.com \
    --to=fransmeulenbroeks@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.