[m-dev.] Packaging repository
paul at bone.id.au
Fri Apr 12 11:53:58 AEST 2013
On Fri, Apr 12, 2013 at 11:45:52AM +1000, Peter Wang wrote:
> On Fri, 12 Apr 2013 10:59:19 +1000, Paul Bone <paul at bone.id.au> wrote:
> > On Fri, Apr 12, 2013 at 10:48:39AM +1000, Peter Wang wrote:
> > > On Thu, 11 Apr 2013 16:31:57 +1000, Paul Bone <paul at bone.id.au> wrote:
> > > > On Thu, Apr 11, 2013 at 04:20:00PM +1000, Peter Wang wrote:
> > > > > You, too, can make some low quality packages:
> > > > > https://github.com/Mercury-Language/packaging
> > > > >
> > > > > We can keep it or not.
> > > >
> > > > Hi Peter,
> > > >
> > > > I've got some half-implemented mercury packaging work here somewhere. I'll
> > > > merge it in if you want.
> > >
> > > Better stick it in another branch if it would conflict.
> > >
> > Ah, what I mean is put my work in your repository manaully (merge the
> > projects) rather than doing any kind of git merge. My package builds only
> > the asm_fast.gc grade (as we didn't have the DEST_DIR support for multiple
> > grades yet) and sticks files of different types in different binary
> > packages. Ie, if you just want to link to a Mercury program you don't need
> > to install the compiler and tools.
> Our goals are different and you might not be able to merge your work
> without detracting from a working script. I don't care about making
> packages ready for inclusion into Debian or whatever. My goal is only
> to lower MTTHW and, for myself, being able to spin up a new VM with a
> working Mercury installation quickly, assuming someone else is
> generating the packages.
Okay, In that case I suggest we use your packages in the short term (and
outside of debian) and use my more experimental ones in the long term, once
they're ready. By 'use' I mean promote (as official) and share publically.
People can use whatever they want :-)
More information about the developers