[Mageia-dev] sync with mandriva

Wed Nov 24 02:01:56 CET 2010

On 19 November 2010 16:21, Bruno Cornec <Bruno.Cornec at hp.com> wrote:
+> Pascal Terjan said on Fri, Nov 19, 2010 at 04:10:30PM +0000:
+>
+>> On Thu, Nov 18, 2010 at 18:11, Maarten Vanraes
+>> <maarten.vanraes at gmail.com> wrote:
+>> > if people keep in mind that sometimes tarballs aren't always fetchable from
+>> > the internetz; then i'm ok with this. also, possibly if the tar is the same as
+>> > the previous version/revision, it could even be fetched from the older
+>> > packages/releases
+>>
+>> Removing it from svn does not mean no longer hosting it, but svn is
+>> not appropriate to keep history of all versions of tarball that have
+>> once existed in cooker
+>
+> That was exactly my original point.
+>
+>> One solution can be for example
+>> - Storing the tarballs matching svn head on a ftp if the src.rpm is
+>> not yet available
+>> - Having the tool that checkouts from svn to also download src.rpm and
+>> extract tarball from there, looking on the ftp if there is not yet a
+>> src.rpm for that version
+>
+> Yes, that's one approach indeed.
+> What is needed IMHO is:
+> for a maintainer to have the tgz (from a flat repo, ftp/http/smb/...)
+> +patches in VCS (SVN, Git, ...) + SPEC in VCS (SVN, Git, ...).
+> mdvsys would just push what is in VCS.
+> The BS should also have the same pointer to the same tgz (checksum
+> verified to be sure e.g. - and kept somewhere for history, compliance,
+> ...reasons)) and to the SVN content.
+
+http://kenobi.mandriva.com/~spuk/binrepo.html#use-of-a-plain-filesystem-storage-for-the-tarballs
+
+-- 
+(nil)
+