public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Stipe Tolj" <tolj@wapme-systems.de>,
	"Charles Wilson" <cwilson@ece.gatech.edu>
Cc: "Gerrit P. Haase" <cygwin@cygwin.com>
Subject: Re: new site for my ports is up
Date: Sun, 11 Nov 2001 08:26:00 -0000	[thread overview]
Message-ID: <05cc01c16e24$2e03bf00$0200a8c0@lifelesswks> (raw)
In-Reply-To: <3BF3C5A2.7F7907B8@wapme-systems.de>

----- Original Message -----
From: "Stipe Tolj" <tolj@wapme-systems.de>


> The only point I have to critic is the lack in tools and mechanisms to
> maintain the packages "on the distribution" (site). I would like to
> see an integrated web site that focuses on two aims:

The site maintenance is actually pretty automatic now. Copy the file to
the location, it's included. Delete the file, it's removed. Hmm that's
easy :}.

>   1) supporting the (new) users the best way to get what they want,
> aka "has someone ported foobar already to Cygwin?!"

Chris has this already - he generates an automatic list of packages on
the cygwin site. See this list a few days back IIRC.

>   2) support the pacakge maintainers, i.e. by having a reference of
> all used files and possible file conflicts within a database on the
> site. A package maintainer should be able to "check-in" a new release
> and roll a regression test on it before it gets publicaly available
> and integrated to setup.ini.

Hmm, I don't agree. See my point about conflicts. Conflicts are normal,
and to be expected. There is no point getting all automated about
detecting conflicts in packages until setup.exe can prevent the users
installing those conflicting packages. Until that point, a check every
month or three will probably suffice. An automated check on the package
when it is put into the repository would also be great, but that takes
tuit and I can think of other things that I'd like Chris to tuit before
this (winsup/utils breakout specifically).

> > Some stuff cannot be distributed from the cygwin mirror system, for
> > legal or political reasons (think cygipc).  [BTW, Gerrit, I have NO
> > problems with you mirroring the cygipc package. Go ahead.  But don't
try
> > to submit it for inclusion in the official dist, 'cause it won't be
> > accepted]
>
> why is that?

cygipc is getting replaced (slowly) by a cygwin-integrated ipc daemon.
(BTW: chris, can you comment on the file layout for that, so that it can
be merged.)

As for other things, it's a case by case basis. Imagine a package that
has legal issues with being distributed from the US, for example.

Rob


--
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 22:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-11  8:26 Gerrit P. Haase
2001-11-11  8:26 ` Charles Wilson
2001-11-11  8:26   ` Christopher Faylor
2001-11-11  8:26     ` Gerrit P. Haase
2001-11-11  8:26       ` Robert Collins
2001-11-11  8:26       ` Stipe Tolj
2001-11-11  8:26         ` Gerrit P. Haase
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       ` Charles Wilson
2001-11-11  8:26         ` John Marshall
2001-11-11  8:26           ` Robert Collins
2001-11-11  8:26             ` Jochen Küpper
2001-11-11  8:26               ` Stipe Tolj
2001-11-11  8:26                 ` Jochen Küpper
2001-11-11  8:26           ` Charles Wilson
2001-11-11  8:26             ` Robert Collins
2001-11-11  8:26               ` Robert Collins
2001-11-11  8:26             ` Christopher Faylor
2001-11-11  8:26               ` Charles Wilson
2001-11-11  8:26               ` Robert Collins
2001-11-11  8:26                 ` Christopher Faylor
2001-11-11  8:26                   ` Robert Collins
2001-11-11  8:26                     ` Christopher Faylor
2001-11-11  8:26         ` Stipe Tolj
2001-11-11  8:26           ` Robert Collins [this message]
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 ` Christopher Faylor
2001-11-11  8:26   ` Christopher Faylor
2001-11-11  8:26     ` Charles Wilson
2001-11-11  8:26       ` Christopher Faylor
2001-11-11  8:26   ` Robert Collins
2001-11-11  8:26     ` Christopher Faylor
2001-11-11  8:26 David A. Cobb

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='05cc01c16e24$2e03bf00$0200a8c0@lifelesswks' \
    --to=robert.collins@itdomain.com.au \
    --cc=cwilson@ece.gatech.edu \
    --cc=cygwin@cygwin.com \
    --cc=tolj@wapme-systems.de \
    /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).