public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: RFC: New build types
Date: Thu, 20 Mar 2008 04:02:34 +0000	[thread overview]
Message-ID: <frsn6m$s1m$2@ger.gmane.org> (raw)
In-Reply-To: 47E032E5.2020301@gentoo.org

Luca Barbato wrote:

> Steve Long wrote:
>> Something that's been discussed on IRC is the idea of a .pbuild file,
>> written in Python. I can also think of .cbuild (C) .Cbuild (C++) .sbuild
>> (Scheme) .hbuild (Haskell) and .jbuild (guess;) as being of immediate
>> use, (although I accept I might be the only one interested in the first
>> ;)
> 
> I do not see any improvement per se.
> 
Well I agree C and C++ aren't very useful, since they are more than
adequately covered by make et al. With the others, there are setup tools
like distutils in the language already.

>> How do others feel about such an addition?
> 
> I think it's pointless.
> 
Fair enough. It's intended to make it easier to write install scripts.


-- 
gentoo-dev@lists.gentoo.org mailing list



      reply	other threads:[~2008-03-20  4:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 10:18 [gentoo-dev] RFC: New build types Steve Long
2008-03-18 10:11 ` Rémi Cardona
2008-03-20  3:59   ` [gentoo-dev] " Steve Long
2008-03-20  5:13     ` Rémi Cardona
2008-03-20  6:51       ` [gentoo-dev] " Steve Long
2008-03-20  7:15         ` Brian Harring
2008-03-21 12:52           ` [gentoo-dev] " Steve Long
2008-03-20 10:44         ` [gentoo-dev] " Petteri Räty
2008-03-21 12:01           ` [gentoo-dev] " Steve Long
2008-03-20  5:31     ` [gentoo-dev] " Marius Mauch
2008-03-18 10:32 ` [gentoo-dev] " Jakub Moc
2008-03-18 21:23 ` Luca Barbato
2008-03-20  4:02   ` Steve Long [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='frsn6m$s1m$2@ger.gmane.org' \
    --to=slong@rathaus.eclipse.co.uk \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox