Mailing List Archive

About packaging CVS versions
Hi,

I am packaging the mythtv, xmltv and further required dependencies in
rpms format. Some time ago (sorry couldn't find a reference) it was
discussed whether it was a good thing to package CVS versions. The
consent back then was not to do so. I think the arguments were that
users would not be able to identify the CVS checkout date in their bug
reports.

I have gotten lately many requests for packaging the CVS versions and
they all have valid reasons to do so (bug fixes, new hardware), so I'd
like to bring this up again.

Would it be acceptable to package CVS versions denoting the checkout
date in the version (or rather the release) field? Something like
mythsomething-0.9-cvs20030614.1?
--
Axel.Thimm@physik.fu-berlin.de
Re: About packaging CVS versions [ In reply to ]
As a Linux newbie I think RPMs or some other easy to install way of packaging
MythTV would be great.

Why not display the version number on the menu screen by default so that
folks who have used the RPMs can easily get thier version number?

Of course more advanced folks can remove that bit if it's too much clutter.

Axel Thimm wrote:
> Hi,
>
>I am packaging the mythtv, xmltv and further required dependencies in
>rpms format. Some time ago (sorry couldn't find a reference) it was
>discussed whether it was a good thing to package CVS versions. The
>consent back then was not to do so. I think the arguments were that
>users would not be able to identify the CVS checkout date in their bug
>reports.
>
>I have gotten lately many requests for packaging the CVS versions and
>they all have valid reasons to do so (bug fixes, new hardware), so I'd
>like to bring this up again.
>
>Would it be acceptable to package CVS versions denoting the checkout
>date in the version (or rather the release) field? Something like
>mythsomething-0.9-cvs20030614.1?
>--
>Axel.Thimm@physik.fu-berlin.de