From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Problem: HOWTOs archive versions
Date: Sat Jul 28 11:35:03 2001 [thread overview]
Message-ID: <01072820355404.04135@localhost> (raw)
In-Reply-To: <20010728112125.C12932@cvs.gentoo.org>
On Saturday 28 July 2001 20:21, you wrote:
> On Sat, Jul 28, 2001 at 08:14:13PM +0300, Dan Armak wrote:
> > Hi all,
> >
> > This is not meant to revive the versioning question.
> >
> > The various app-doc/howto ebuilds (by pm) have no versions, because the
> > standard howto archives have none. The ebuilds define version 1.0
> > arbitrarily, but they always download the newest archive with the same
> > address and filename.
> >
> > Do you think we should manage this situation in a better way?
> >
> > Should we try to work with setting the version dynamically at merge time
> > to the archive's timestamp?
>
> Best solution for right now is to create our own version of the archive
> with a timestamp, and write the linuxdoc people to create these archives
> with a timestamp (20010728, for example) as the version number:
>
> linux-howto-20010728.tar.gz
OK, but I forgot to introduce the more important question: what about
checksums (i.e. message digests)? Should we check for & create a new ebuild
for a new timestamp every week or so, or should we override checksums? And
how do you override them?
--
Dan Armak
Gentoo Linux Developer
Matan, Israel
next prev parent reply other threads:[~2001-07-28 17:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-28 11:14 [gentoo-dev] Problem: HOWTOs archive versions Dan Armak
2001-07-28 11:22 ` Daniel Robbins
2001-07-28 11:26 ` Dan Armak
2001-07-28 11:35 ` Dan Armak [this message]
2001-07-28 13:16 ` Dan Armak
2001-07-28 17:39 ` Daniel Robbins
2001-07-29 1:13 ` Dan Armak
2001-07-29 11:19 ` Dan Armak
2001-07-29 12:11 ` Parag Mehta
2001-07-29 12:35 ` Dan Armak
2001-07-29 16:07 ` Daniel Robbins
2001-07-29 16:23 ` Dan Armak
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=01072820355404.04135@localhost \
--to=danarmak@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox