[gentoo-dev] Re: Help with ebuild -- agsatellite

[gentoo-dev] Re: Help with ebuild -- agsatellite

[Seemant Kulleen]

Hi Georges,

OK, building the MD5 info by hand actually worked.  Now, the problem still remains, that if this ebuild makes it into portage, users will have to do the same.  The digesting should actually happen automatically, no?

Thanks,

Seemant

Re: [gentoo-dev] Re: Help with ebuild -- agsatellite

[George Shapovalov]

Hi

When you test your ebuild I guess you anyway put it in proper place and 
produce all necessary files (the minimum would be ebuild_file and 
files/digest-pkg, looks like all packages now contain ChangeLog as well).
Just tar em all in one tar.gz (or bz2, not an issue here I guess) and submit 
that (as described in howto, using bugzilla). User has to have digest file 
_before_ downloading the source, so someone, in this case you, have to be 
authority in that respect, otherwise it is pointless. 
   This is the way I submitted ebuilds. If anybody does it differently, 
please comment.
   There seems to be a problem woth attaching files thoug. You will need to 
either emeil assigned gentoo-developer with this package later on or, if you 
can, put it somewhere up and provide url (http/ftp) in description of the 
package. That is if things won't work out as they should.

George


On Thursday 21 February 2002 19:37, you wrote:
> Hi Georges,
>
> OK, building the MD5 info by hand actually worked.  Now, the problem still
> remains, that if this ebuild makes it into portage, users will have to do
> the same.  The digesting should actually happen automatically, no?
>
> Thanks,
>
> Seemant
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] Re: Help with ebuild -- agsatellite

[Tod M Neidt]

On Thu, 2002-02-21 at 21:37, Seemant Kulleen wrote:
> Hi Georges,
> 
> OK, building the MD5 info by hand actually worked.  Now, the problem still remains, that if this ebuild makes it into portage, users will have to do the same.  The digesting should actually happen automatically, no?
> 
You can create digests by 'ebuild foo.ebuild digest', this is what a
developer will do before he commits an ebuild to cvs.

If you put both URLs in the SRC_URI string like I suggested earlier both
tarballs will be included in the digest.

Hope that helps,

tod