public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stipe Tolj <tolj@wapme-systems.de>
To: Robert Collins <robert.collins@itdomain.com.au>
Cc: Corinna Vinschen <cygwin@cygwin.com>
Subject: Re: no more package moratorium?
Date: Sun, 11 Nov 2001 08:26:00 -0000	[thread overview]
Message-ID: <3BF450A3.2FEFAB14@wapme-systems.de> (raw)
In-Reply-To: <06fc01c16e2d$7169d730$0200a8c0@lifelesswks>

> We've had that - setup.ini was the database, and updating was a PITA,
> because it couldn't be easily distributed. Setup.hint allows the
> metadata to be altered by the maintainer - without needing a central
> repository.

I agree, that's why I mentioned in the file conflict thread:

The package maintaining system should provide _mechanisms_ to support
the package maintainers.

It would be easy to allow package maintainers (via HTTP basic
authentification and underlying PHP application) to update the
relevant information in the database.

This is how my intension from the package maintaining module looks
like.
 
> Also, federating a database is _hard_. Federating package metadata by
> associating it with the packages is trivial.

It depends on the design of the database and the access mechanisms,
IMO.

Stipe

tolj@wapme-systems.de
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info@wapme-systems.de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2001-11-15 23:32 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 12:06 Gareth Pearce
2001-11-02 12:19 ` Robert Collins
2001-11-11  8:26   ` Corinna Vinschen
2001-11-11  8:26     ` Jan Nieuwenhuizen
2001-11-11  8:26       ` Markus Hoenicka
2001-11-11  8:26         ` Stipe Tolj
2001-11-11  8:26           ` Charles Wilson
2001-11-11  8:26             ` Christopher Faylor
2001-11-11  8:26       ` Stipe Tolj
2001-11-11  8:26         ` Robert Collins
2001-11-11  8:26           ` Stipe Tolj
2001-11-11  8:26             ` Robert Collins
2001-11-11  8:26               ` Stipe Tolj [this message]
2001-11-11  8:26                 ` Robert Collins
2001-11-11  8:26                   ` Christopher Faylor
2001-11-11  8:26                   ` Stipe Tolj
     [not found]       ` <m3k7wr50fa.fsf@appel.lilypond.org>
2001-11-11  8:26         ` tetex-beta nitpicking [WAS: Re: no more package moratorium?] Markus Hoenicka
2001-11-11  8:26           ` Charles Wilson
2001-11-11  8:26             ` Markus Hoenicka
2001-11-11  8:26           ` Jan Nieuwenhuizen
2001-11-11  8:26             ` Robert Collins
2001-11-11  8:26           ` Jan Nieuwenhuizen
2001-11-11  8:26             ` Charles Wilson
2001-11-11  8:26               ` Jan Nieuwenhuizen
2001-11-11  8:26             ` Markus Hoenicka
2001-11-11  8:26               ` Robert Collins
2001-11-11  8:26                 ` Markus Hoenicka
2001-11-11  8:26                   ` Jerome BENOIT
2001-11-11  8:26                     ` Robert Collins
2001-11-11  8:26     ` no more package moratorium? Robert Collins
2001-11-11  8:26       ` Christopher Faylor
2001-11-11  8:26         ` Robert Collins
2001-11-11  8:26         ` Jesper Eskilson
2001-11-11  8:26           ` Christopher Faylor
2001-11-11  8:26             ` Stipe Tolj
2001-11-11  8:26         ` Stipe Tolj
2001-11-11  8:26       ` Stipe Tolj
2001-11-11  8:26       ` Robert Collins
2001-11-11  8:26   ` Robert Collins
2001-11-11  8:26 ` Gareth Pearce
2001-11-11  8:26 E

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BF450A3.2FEFAB14@wapme-systems.de \
    --to=tolj@wapme-systems.de \
    --cc=cygwin@cygwin.com \
    --cc=robert.collins@itdomain.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).