On Thu, 28 May 2015 20:06:28 +0200 Tristan Gingold <[email protected]> wrote:
> On 27/05/15 21:38, Adam Jensen wrote: > > On Wed, 27 May 2015 21:14:58 +0200 > > Tristan Gingold <[email protected]> wrote: > > > >> Creating a source tarball should be very easy: checkout the trunk and > >> create the tar. But maybe you want a release number rather than a > >> snapshot. In that case, we need to create a branch. > >> > >> Certainly not a big deal. > > > > A versioned, hosted, canonical release of GHDL(GCC-4.9) would be very > > helpful to package developers. A FreeBSD port (and possibly a DragonFlyBSD > > port) can't move forward without it. > > > > I don't think I have adequate access to the GHDL sourceforge repo (or an > > adequate understanding of GHDL's project management and release engineering > > process) to make a release. But if one of the core developers would go > > through that exercise, BSD port development could move forward. > > Brian, what do you think about that ? > I imported the mercurial GHDL repo from sourceforge into a github account, here: https://github.com/hanzer/GHDL FreeBSD ports natively handle github; even if there isn't a release, any git hash will do. It might take a little time to get the automated synchronization set up (the github repo was created about an hour ago) but it might turn out to be a usable workaround for the lack of regular tarball releases. _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
