[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian vs. BOGUS




On Mon, 4 Sep 1995, Karl Eichwalder wrote:

> >>>>> "Richard" == Richard Kettlewell <richard@elmail.co.uk> writes:
> 
>     Bruce> The location of the source,
> 
>     Richard> Sure; but why does that mean it has to be in the output
>     Richard> from dpkg?
> 
> If nobody likes the idea (or it's too complicate to implement)--forget
> about it.  But I'm sure, it's useful.
> 
>     Richard> We already do this on ftp.debian.org, modulo Debianising
>     Richard> diffs.  Are you suggesting we do this for upstream sources
>     Richard> as well?
> 
> Since you are asking: Yes, of course, e.g.,
> 
>     FTP: ftp.debian.org:/.../untouched-sources/vixie-cron-3.x.tar.gz
> 
> Karl
> 
> 
 Hmmm. So far I didn't notice that debianized sources were that different.
 The paths are normally changed (eg. many packages tend to place themselves
 in /usr/local/(s)bin, instead of debian's /usr/(s)bin), CFLAGS and install 
 targets -- sometimes.  Normally README.debian contains the log, and you can
 track down the changes, if you really wish. Anyway, you could just type
 'make' instead of 'debian.rules binary' and see what happens.  And the
 original readme's supposed to include an ftp addres of the package's 
 primary  site, or you can use archie to track it down.  Besides, people 
 who run ftp servers may not have unlimited disk space to store everything.
 Really, what does this gain? ( R. Kettlewell)

Besides, this whole business of dselect/dpkg, pkgtool (Slackware) etc. is
for that "average user" who doesn't know how to manually set up a Linux box.
If you do, you don't have to stick to a distribution ( and then you probably
know how to track down the sources, hack Makefiles and all that :-)
And all that info (which sometimes scrolls up too fast, too) can actually
be confusing, I suppose...


Dimitri


Reply to: