[EMAIL PROTECTED] said:
> The DELTA file is described by Bruce as containing patch input. I'm
> thinking it'd be better to have it contain a script to debianize the
> sources. The patch input itself (and perhaps multiple patch inputs
> for the multiple upstream sources) could be contained inte
On Tue, 31 Oct 1995, James A. Robinson wrote:
> Now hold on a second there! What about packages put together from
> multiple sources? Say MH with Linux patchs? I don't want to deal
> with writing something that will be able to intelligently do the
> patchs needed and then make the source.
Tha
> So if we start from the assumption that we will have a separate, totally
> unmodified source .tar.gz, that means we will have at a minimum two files.
>
> So, what can we have that other file to be?
>
> I would propose that it be a script (humanly readable, though it doesn't
> have to be the p
> I'll go further and say that I think that any approach that does not
> include as one of its goals the ability to work with totally virgin source
> archives is a total waste of time because it doesn't buy us enough to
> justify the work.
Now hold on a second there! What about packages put tog
Michael Alan Dorman <[EMAIL PROTECTED]> said:
> I'll go further and say that I think that any approach that does not
> include as one of its goals the ability to work with totally virgin source
> archives is a total waste of time because it doesn't buy us enough to
> justify the work.
On Tue, 31 Oct 1995, David Engel wrote:
>First, I prefer to go with unmodified, upstream source. Second, I
>really mean unmodified, i.e.. the Debianizing script (or whatever) must
>take care of unpacking into subdirectories, if necessary.
I'll go further and say that I think that any approach t
> > 2. It would also be good to have the same thing as above, but to
> > produce the upstream source.
> > 2a. That upstream source should be unmodified.
>
> A 'unmodified upstream source + unpack/patch thingy' would not conflict
> with 1(alt).
>
> > 3. All of the ways of unpacking our source pack
> Before we get bogged down into the details of exactly what script
> should do what, &c, we need to consider what our requirements are, and
> make some overall design decisions. I think we have several
> conflicting requirements.
>
> 1. It is important to have a single file that can be downloade
Ian Jackson <[EMAIL PROTECTED]>> said (quoting out of order):
> [...] we need to consider what our requirements are, and
> make some overall design decisions. I think we have several
> conflicting requirements.
> 2a. That upstream source should be unmodified.
> 3. All of the ways of unpacking o
Before we get bogged down into the details of exactly what script
should do what, &c, we need to consider what our requirements are, and
make some overall design decisions. I think we have several
conflicting requirements.
1. It is important to have a single file that can be downloaded and
then u
10 matches
Mail list logo
