http://www.lojadotelemovel.com/images/riscado_cinza.gif";>
http://www.lojadotelemovel.com/mailing/images/logo.jpg";
width="580" height="49">
http://www.lojadotelemovel.com/mailing/images/topo.jpg"; width="580"
height="93">
On Mon, May 13, 2002 at 10:42:02AM -0500, Manoj Srivastava wrote:
> >>"Anthony" == Anthony Towns writes:
> Anthony> There is _absolutely_ no call for other packaging tools, and
> Anthony> absolutely _no_ need for a standard to make this easy or
> Yeah, right. There is never any need for co
Stefano Zacchiroli (2002-05-11 00:30:54 +0200) :
> I suggests:
> * Multiple configure-make cycles
>
> For reference have a look to a thread of some weeks ago on
> debian-mentors with the same subject, the first message id of the thread
> was <[EMAIL PROTECTED]>; one example reported in this
> thre
>>"Anthony" == Anthony Towns writes:
Anthony> Julian, please note the above: this is "who's talking about
Anthony> dpkg anyway".
This is getting no where fast.
Anthony> There is _absolutely_ no call for other packaging tools, and
Anthony> absolutely _no_ need for a standard to make
On Mon, May 13, 2002 at 01:45:33AM -0500, Manoj Srivastava wrote:
> >>"Anthony" == Anthony Towns writes:
> >> *Sigh*. Let me see if I can dot the i's and cross the t's. A
> >> package should be buildable using the bits mentioned in policy. Any
> >> package may, however, choose to add any extra
On Mon, May 13, 2002 at 01:29:59AM -0500, Manoj Srivastava wrote:
> >>"Anthony" == Anthony Towns writes:
> Anthony> The documentation should be found wherever the dpkg
> Anthony> maintainers want it, not wherever the -policy maintainers
> Anthony> think might be fun.
> What policy contai
>>"Anthony" == Anthony Towns writes:
Anthony> On Mon, May 06, 2002 at 05:19:09PM -0500, Manoj Srivastava wrote:
>> >>"Anthony" == Anthony Towns writes:
Anthony> The real question is whether maintainers are meant to build
Anthony> using the features of dpkg, or the ones listed in
>> *Sigh*.
>>"Bob" == Bob Hilliard <[EMAIL PROTECTED]> writes:
Bob> Most of the documentation emphasizes debhelper, but the
Bob> possibility of writing a rules file by hand should be mentioned.
Bob> Any description of hand-crafted rules files should mention the
Bob> sample rules files availa
>>"Anthony" == Anthony Towns writes:
Anthony> The documentation should be found wherever the dpkg
Anthony> maintainers want it, not wherever the -policy maintainers
Anthony> think might be fun.
What policy contains won't be documentation. It shall be a
standard interface that must be
9 matches
Mail list logo
