cvs commit: ports/net-im/openfire Makefile distinfo pkg-plist ports/net-im/openfire/files patch-build-build.xml

Alexandr Kovalenko alexandr.kovalenko at
Tue Jan 11 11:32:31 UTC 2011

On Tue, Jan 11, 2011 at 1:11 PM, Pietro Cerutti <gahr at> wrote:
> On 2011-Jan-11, 12:01, Alexandr Kovalenko wrote:
>> On Tue, Jan 11, 2011 at 10:13 AM, Pietro Cerutti <gahr at> wrote:
>> > On 2011-Jan-10, 20:33, Alexandr Kovalenko wrote:
>> >> Beta?
>> >>
>> >> May I ask, why this went into net-im/openfire port, but not to new
>> >> port net-im/openfire-devel ?
>> >
>> > Ok, I guess I owe an explanation here, since quite a few people have
>> > raised concerns about me committing a beta version to openfire/.
>> >
>> > I am personally against -devel ports. These tends to get marked as
>> > IGNORE or anyway no longer be valid after the -devel branch has turned
>> > to stable. I prefer to keep the latest available version in myport/,
>> > upon user request, keep previous (stable and maintained) versions in
>> > myport10, myport11, etc... See for example java/netbeans, java/netbeans5,
>> > java/netbeans55, java/netbeans61. This brings two advantages:
>> >
>> > - the cost of maintaining a previous version in myport10/ is ~= 0
>> > - the myport/ directory always contains the latest available version
>> >
>> > It is a porter's discretion to ponder wheter a particular release
>> > version is stable enough to get into the main myport/ directory.
>> >
>> > In this particular case, openfire-3.7.0.beta seemed to my workable enough.
>> Can you understand, that many of people use ports in production
>> systems (surprise!) and expect NO beta versions in non -devel ports,
>> no sudden breakage of their systems without any notice in UPDATING and
>> so on, whatever you personally think about that. Ports system is not
>> your personal sandbox/private branch of ports. It is what people use
>> on their production systems.
>> If you want to commit beta, you have 2 choices:
>> 1. Wait until non-beta to commit.
>> 2. Commit beta to -devel port after repocopy.
> OK, first off let me tell you that I don't like at all the tone of your
> email.

I'm sorry for that, it wasn't supposed to be offensive. I'm just a bit
nervous after breakage which I went into after upgrading this port and
I agree that tone of the e-mail was not completely correct.
My appologies.

> That being said, I agree that my view of -devel ports might be a bit
> personal and might not be shared by the majority of users. For this
> reason, I'll do as you suggest:
> - backport 3.6.0 into net-im/openfire
> - create a net-im/openfire-devel for 3.7.0.beta
> I hope this solves all your problems.

Thank you very much.

P.S. I suppose _after_ 3.7.0 _stable_ release it may be acceptable to
go 2 different ways:

1. Create net-im/openfire37 leaving alone net-im/openfire
2. Repocopy net-im/openfire to net-im/openfire36 and commit of 3.7.0
into net-im/openfire with adding note in UPDATING

To clarify - I'm not against seeing 3.7.0 in net-im/openfire, but
against -beta there or appear it there without notice in UPDATING at
least, because 3.6.x and 3.7.x are not completely backward compatible.

Thanks for your time and work you are making for FreeBSD :)

Alexandr Kovalenko

More information about the cvs-all mailing list