public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Problem: HOWTOs archive versions
Date: Sun Jul 29 01:13:01 2001	[thread overview]
Message-ID: <0107291013030A.04135@localhost> (raw)
In-Reply-To: <20010728173811.B21210@cvs.gentoo.org>

On Sunday 29 July 2001 02:38, you wrote:
> On Sat, Jul 28, 2001 at 08:35:54PM +0300, Dan Armak wrote:
> > > 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?
>
> Nothing special needs to be done with the message digests.  We just upload
> the file to our ibiblio mirror.
>

I've been talking with a man from the LDP. Apparently these archives are 
updated at least every few days, and potentially whenever any individual 
howto is updated. So, we can either override checksums - that is, tell 
portage no checksums are needed, as long as the archives exctracts correctly. 
Or, we can generate the correct checksum on-the-fly from within the ebuild 
and have portage reference that. Finally, we might have a program on the 
gentoo server that would check for new versions every day and update the 
checksums, but it's making too big a deal of it. 

As for versioning: I believe (I'm still waiting for the LDP guy's 
confirmation) that an index file inside the archive is always autogenerated 
when the archive is autogenerated. We can use its mtime data to add a 
timestamp as an ebuild version.
Is there a problem with setting/overriding PV from within an ebuild?

-- 

Dan Armak
Gentoo Linux Developer
Matan, Israel



  reply	other threads:[~2001-07-29  7:12 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
2001-07-28 13:16     ` Dan Armak
2001-07-28 17:39     ` Daniel Robbins
2001-07-29  1:13       ` Dan Armak [this message]
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=0107291013030A.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