Re: version control systems

From	John Hasler <jhasler@newsguy.com>
Newsgroups	alt.os.linux, alt.os.linux.debian
Subject	Re: version control systems
Date	2015-12-30 08:15 -0600
Organization	Dancing Horse Hill
Message-ID	<87fuyk6mzl.fsf@thumper.dhh.gt.org> (permalink)
References	(1 earlier) <87ege6r7oz.fsf@thumper.dhh.gt.org> <n5sr2k$a9e$1@dont-email.me> <deeu36Fpr3rU1@mid.individual.net> <87a8otpbm6.fsf@thumper.dhh.gt.org> <n60aqo$reo$1@dont-email.me>

Cross-posted to 2 groups.

Show all headers | View raw

I wrote:
> Each package is a seperate unit.  Dependency relationships among
> packages are handled on the package level and described by
> standardized metadata in each package.

crankypuss writes:
> IMO that is *extremely* messed up.

I wrote:
> This makes it possible to build and upload to the archive a new
> version of a package without necessarily making any changes to any
> other package.

crankypuss writes:
> Dependency relationships should be generated from the code, not from
> the developer's memory or inclinations to "recommend" this or that.
> Dependencies are simply what they are, the information is there in the
> source.

Wrong.  The programs in different packages are only related at the
process level (except for libraries, and there is automation for that).
Sometimes the dependency is only at the documentation level, or even
only at the user requirements level.  In many cases it would be possible
to totally rewrite a package in a different language without impacting
any dependencies.  Dependencies operate off of the Debian version
number, not file hashes.

Also understand that dependencies are there for the use of the package
management system running on your machine, not for the use of some
central build system.  Consistency in the Testing and Stable archives is
enforced by not allowing a package to transition from Unstable to Testing
until all of its dependencies can be satisfied (the archive management
software handles that).

Debian dependencies are much more complex than the simple "if it changes
rebuild" of a typical revision control system.  There can be ranges,
exclusions, conflicts, provides, and virtual packages, for example.  A
new version of a library may or may not require that packages using it be
rebuilt: the so number tells you that.

BTW you are free to ignore "Recommends".  That is why they are called
that.
-- 
John Hasler 
jhasler@newsguy.com
Dancing Horse Hill
Elmwood, WI USA

Thread

version control systems crankypuss <invalid@invalid.invalid> - 2015-12-28 04:50 -0700
  Re: version control systems "J.O. Aho" <user@example.net> - 2015-12-28 13:56 +0100
  Re: version control systems John Hasler <jhasler@newsguy.com> - 2015-12-28 08:03 -0600
    Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-28 19:30 -0700
      Re: version control systems John Hasler <jhasler@newsguy.com> - 2015-12-28 21:31 -0600
        Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-29 06:59 -0700
          Re: version control systems John Hasler <jhasler@newsguy.com> - 2015-12-29 08:47 -0600
            Re: version control systems Chris Ahlstrom <OFeem1987@teleworm.us> - 2015-12-29 19:42 -0500
            Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-30 03:01 -0700
              Re: version control systems mm0fmf <none@mailinator.com> - 2015-12-30 10:35 +0000
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-30 04:41 -0700
                Re: version control systems Jasen Betts <jasen@xnet.co.nz> - 2015-12-30 20:19 +0000
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-31 02:28 -0700
                Re: version control systems Jasen Betts <jasen@xnet.co.nz> - 2015-12-31 20:46 +0000
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-31 23:12 -0700
                Re: version control systems Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-01-01 11:40 -0500
                Re: version control systems Mark Carroll <mtbc@ixod.org> - 2016-01-01 17:16 +0000
                Re: version control systems Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-01-01 13:37 -0500
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2016-01-01 15:01 -0700
                Re: version control systems Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-01-01 19:19 -0500
                Re: version control systems Jasen Betts <jasen@xnet.co.nz> - 2016-01-02 02:45 +0000
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2016-01-02 01:33 -0700
                Re: version control systems Kirk_Von_Rockstein <Kirk_Von_Rockstein@nowhere.invalid> - 2016-01-04 00:55 +0000
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2016-01-04 03:38 -0700
                Re: version control systems Mark Carroll <mtbc@ixod.org> - 2016-01-04 12:19 +0000
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2016-01-04 11:19 -0700
              Re: version control systems Chris Ahlstrom <OFeem1987@teleworm.us> - 2015-12-30 05:58 -0500
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-30 04:50 -0700
                Re: version control systems Chris Ahlstrom <OFeem1987@teleworm.us> - 2015-12-30 08:02 -0500
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-30 06:43 -0700
                Re: version control systems mm0fmf <none@mailinator.com> - 2015-12-30 14:42 +0000
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-30 12:14 -0700
              Re: version control systems John Hasler <jhasler@newsguy.com> - 2015-12-30 07:30 -0600
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-30 06:55 -0700
      Re: version control systems "J.O. Aho" <user@example.net> - 2015-12-29 09:20 +0100
        Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-29 07:03 -0700
        Re: version control systems John Hasler <jhasler@newsguy.com> - 2015-12-29 08:34 -0600
          Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-30 03:17 -0700
            Re: version control systems Chris Ahlstrom <OFeem1987@teleworm.us> - 2015-12-30 05:59 -0500
              Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-30 04:53 -0700
              Re: version control systems Richard Kettlewell <rjk@greenend.org.uk> - 2015-12-30 12:07 +0000
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-30 05:20 -0700
                Re: version control systems Chris Ahlstrom <OFeem1987@teleworm.us> - 2015-12-30 08:05 -0500
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-30 06:45 -0700
                Re: version control systems Richard Kettlewell <rjk@greenend.org.uk> - 2015-12-30 13:59 +0000
                Re: version control systems John Hasler <jhasler@newsguy.com> - 2015-12-30 08:28 -0600
                Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-30 12:21 -0700
            Re: version control systems John Hasler <jhasler@newsguy.com> - 2015-12-30 07:45 -0600
              Re: version control systems John Hasler <jhasler@newsguy.com> - 2015-12-30 08:30 -0600
                Re: version control systems Chris Ahlstrom <OFeem1987@teleworm.us> - 2015-12-30 14:28 -0500
              Re: version control systems Chris Ahlstrom <OFeem1987@teleworm.us> - 2015-12-30 14:28 -0500
            Re: version control systems John Hasler <jhasler@newsguy.com> - 2015-12-30 08:15 -0600
              Re: version control systems crankypuss <invalid@invalid.invalid> - 2015-12-30 12:53 -0700
                Re: version control systems mm0fmf <none@mailinator.com> - 2015-12-30 20:33 +0000

csiph-web