Ruben Van Boxem wrote: > Honestly, that's out of the scope of what I want to do. > > I am working on... *working on*... a set of build scripts for common > libraries, and plan on uploading them as packages, but not having > anything like mingw-get. > > This isn't a bad idea though, but it does take *a lot* of work to do > correctly. > > Perhaps we can "steal" off of mingw-get itself, but I honestly don't > know how it works. >
I'm hoping to get to a wiki page on how to setup a repository for mingw-get to use but it is documented well in the /var/lib/data/mingw-get/defaults.xml file which sets up a profile, repository and subsystem names. The defaults.xml file suggest renaming itself to profile.xml and modified by the user. So setting up the profile for mingw64 shouldn't be too difficult and I would be happy to see this happen. More difficult is the file name parsing to determine which file is newer. The file name has specific heuristics that should be followed. These are documented at http://www.mingw.org/PackageIdentificationHOWTO but maybe slightly out of date, I'll have to check that when Keith gets back from vacation. Earnie ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
