Re: Subpackaging

2000-08-19 Thread Dwayne C . Litzenberger
> And maybe > prevent installing any 'non-newbie' packages > ("Sorry, your system level is set to 'newbie'. To install > 'complex-manually-configured-package', you must turn this off first) > [And if you can't figure out how to turn it off, you are too newbie] Uh... how about we avoid hand

Re: Subpackaging (Was: Potato now stable)

2000-08-19 Thread Bernhard R. Link
On Fri, 18 Aug 2000, Edward Betts wrote: > I agreed with everything else that you said, you give a good example of how > subpackaging could be implemented using dpkg. However, one of my concerns as a > low bandwidth user is transferring stuff. Great, I can split my debs up into >

Re: Subpackaging (Was: Potato now stable)

2000-08-18 Thread Edward Betts
Anthony Towns wrote: > On Thu, Aug 17, 2000 at 08:58:31PM +0100, Edward Betts wrote: > First, including each architecture and source in every .deb suddenly > balloons our 3 CD set to get i386 binaries to a ~15 CD set. It also > kills non-broadband net upgrades (you *really* want to download six >

Re: Subpackaging (Was: Potato now stable)

2000-08-18 Thread Edward Betts
s likely to at least lost all the optional > components (copyrights, docs, manpages...). There is that, I admit. I agreed with everything else that you said, you give a good example of how subpackaging could be implemented using dpkg. However, one of my concerns as a low bandwidth user is tran

Re: Subpackaging

2000-08-18 Thread Seth Cohn
On Fri, 18 Aug 2000, Anthony Towns wrote: > It's not *entirely* clear that including the above in the .deb itself > is even the best way of doing things though. Everything in the above > is entirely package-independent except for the "doc" lines, and they > can be determined simply by saying "ever

Re: Subpackaging (Was: Potato now stable)

2000-08-17 Thread Anthony Towns
On Thu, Aug 17, 2000 at 08:58:31PM +0100, Edward Betts wrote: > How about a little brainstorming to pick some categories that could be used > in debian. > > Possible layout > ~~~ > control.tar.gzpackage system stuff, depends, postinst, etc > signatures.tar.gz signat

Re: Subpackaging (Was: Potato now stable)

2000-08-17 Thread Edward Betts
Edward Betts <[EMAIL PROTECTED]> wrote: > How would it be implemented? > > My recommendation would be one directory per package. Each subpackage could > just be part of a .tar.gz file. Having the binary dependent parts listed here > would imply that the package locate c

Re: Subpackaging (Was: Potato now stable)

2000-08-17 Thread Edward Betts
Decklin Foster <[EMAIL PROTECTED]> wrote: > I like the plan a lot. some thoughts: Glade to hear it. > I wonder if the default docs should not go in a locale/ subdir for the > proper language (English for most of what exists now). I know very > little about i18b so I won't comment on the implement

Re: Subpackaging (Was: Potato now stable)

2000-08-17 Thread Decklin Foster
Edward Betts writes: > Possible layout > ~~~ I like the plan a lot. some thoughts: > doc/examples.tar.gz /usr/share/doc/examples/* > locale/*/gettext.tar.gz gettext translations I wonder if the default docs should not go in a locale/ subdir for the proper language (English

Subpackaging (Was: Potato now stable)

2000-08-17 Thread Edward Betts
Drake Diedrich <[EMAIL PROTECTED]> wrote: >Under the Irix packaging system (quite nice UI except that it has to > handle Irix packages..) packages exist in a hierarchy, with lowest level > packages quite fine grained. For example: > > I fw_bzip2 02/28/2000 bzip2-0.9.0c Compress/