| 1 |
On Sunday 29 July 2001 02:38, you wrote: |
| 2 |
> On Sat, Jul 28, 2001 at 08:35:54PM +0300, Dan Armak wrote: |
| 3 |
> > > Best solution for right now is to create our own version of the archive |
| 4 |
> > > with a timestamp, and write the linuxdoc people to create these |
| 5 |
> > > archives with a timestamp (20010728, for example) as the version |
| 6 |
> > > number: |
| 7 |
> > > |
| 8 |
> > > linux-howto-20010728.tar.gz |
| 9 |
> > |
| 10 |
> > OK, but I forgot to introduce the more important question: what about |
| 11 |
> > checksums (i.e. message digests)? Should we check for & create a new |
| 12 |
> > ebuild for a new timestamp every week or so, or should we override |
| 13 |
> > checksums? And how do you override them? |
| 14 |
> |
| 15 |
> Nothing special needs to be done with the message digests. We just upload |
| 16 |
> the file to our ibiblio mirror. |
| 17 |
> |
| 18 |
|
| 19 |
I've been talking with a man from the LDP. Apparently these archives are |
| 20 |
updated at least every few days, and potentially whenever any individual |
| 21 |
howto is updated. So, we can either override checksums - that is, tell |
| 22 |
portage no checksums are needed, as long as the archives exctracts correctly. |
| 23 |
Or, we can generate the correct checksum on-the-fly from within the ebuild |
| 24 |
and have portage reference that. Finally, we might have a program on the |
| 25 |
gentoo server that would check for new versions every day and update the |
| 26 |
checksums, but it's making too big a deal of it. |
| 27 |
|
| 28 |
As for versioning: I believe (I'm still waiting for the LDP guy's |
| 29 |
confirmation) that an index file inside the archive is always autogenerated |
| 30 |
when the archive is autogenerated. We can use its mtime data to add a |
| 31 |
timestamp as an ebuild version. |
| 32 |
Is there a problem with setting/overriding PV from within an ebuild? |
| 33 |
|
| 34 |
-- |
| 35 |
|
| 36 |
Dan Armak |
| 37 |
Gentoo Linux Developer |
| 38 |
Matan, Israel |
Archives