* you can have metadata-less filetree and metadata-full(?) filetree
* metadata are version information like the author name, versions of
packages, parent versions, etc.
* metadata-less do not store such information as it is assumed that the
information is stored elsewhere (e.g. in git history)
* gitfiletree is just a filetree format, which in addition performs git commits
of the exported files via shell execution of Git executable
* gitfiletree can operate both in metadata, and metadata-less mode (the latter
is preferable, otherwise you'll have an endless barrage of merge conflicts)
* iceberg is metadata-less filetree only, and performs git commits using libgit
So yes, the format is the same and you can even use gitfiletree and iceberg at
the same time from e.g. different images.
Peter
On Sun, Jul 30, 2017 at 12:11:48PM -0300, Esteban A. Maringolo wrote:
> Hi all
>
> Sorry to Norbert for hijacking this post, but I'd also like to move
> some of my projects to Github, I used Peter's scripts in the past, but
> one thing I don't understand is how to automatically convert a
> ConfigurationOf to a BaselineOf, and if this is really necessary.
>
> Is the FileTree format, as used by filetree and gitfiletree MC repos,
> 100% compatible with the repository format of Iceberg? It seems so to
> me, but it's better to ask than be sorry.
>
> Regards!
>
> Esteban A. Maringolo
>
>
> 2017-07-30 11:35 GMT-03:00 Peter Uhnak <i.uh...@gmail.com>:
> >>
> >> If I've understood correctly, this means you can rage master with a
> >> version number like v1.1 and then put that in the URL
> >>
> >> > https://github.com/peteruhnak/IconFactory/tree/master:v1.1/
> >>
> >
> > I am not sure where you got this url from, but combining branch and tag
> > name makes nor sense... that's like you wanted a version 1.1 AND 2.3 (or
> > whatever would be the latest in master).
> >
> > (as mentioned in the syntax: branch name OR commit id OR tag id)
> >
> > Peter
> >
>
