Jan Kundrát wrote: > Alin Năstac wrote: > >> The upstream doesn't offer a source tarball, so I need to construct >> it myself from their svn repository. >> > > If you're creating a live ebuild, there are already existing eclasses > that works from the user's POV. > I'm not speaking about live ebuilds, only about building a source tarball for a specific version where upstream doesn't offer such thing. > If your aim is to create an ebuild for a specific version, you might as > well checkout stuff yourself and let Gentoo mirror the generated tarball > (your mail doesn't talk about RESTRICT=fetch). If you let Gentoo mirror > the tarball, users are likely to be happier because they'll get the file > faster and in a more reliable way. > What I want is a function that creates the source tarball, based on whatever developer needs for that (the most usual case is a tag export from a svn/cvs repository). The tarball will be placed on Gentoo mirrors at the end (users will not run this new function, only the maintainer). See app-mobilephone/bitpim ebuild example, it will speak for itself.
This can be solved also through an external script, but IMO this solution is ugly. Ebuilds should contain whatever is needed for their maintenance.
signature.asc
Description: OpenPGP digital signature
