public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Problem: HOWTOs archive versions
Date: Sun Jul 29 16:07:02 2001	[thread overview]
Message-ID: <20010729160603.A4474@cvs.gentoo.org> (raw)
In-Reply-To: <0107291013030A.04135@localhost>; from danarmak@gentoo.org on Sun, Jul 29, 2001 at 10:13:03AM +0300

On Sun, Jul 29, 2001 at 10:13:03AM +0300, Dan Armak wrote:

> 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?

Yes.  The best way is to grab one, change the name and upload it to ibiblio.org.
I'm not going to be hacking at Portage to deal with archives with no version numbers;
the problem is with the archive that doesn't have a version number, not Portage.

BTW, you may want to suggest that their archive generation script be upgraded so
that the generated archives have an attached version number or date.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			



  parent reply	other threads:[~2001-07-29 22:06 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
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 [this message]
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=20010729160603.A4474@cvs.gentoo.org \
    --to=drobbins@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