public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: 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: <20011117175553.GA23825@redhat.com> (raw)
In-Reply-To: <3BF6A2A0.5030507@ece.gatech.edu>

On Sat, Nov 17, 2001 at 12:47:12PM -0500, Charles Wilson wrote:
>
>>>No.  No multiple packages in the same directory.  Every package gets
>>>their own directory.
>>>
>>
>>Just to clarify: By "no multiple packages", I mean that I don't want to
>>see (to pick an extreme example) ash-blah.tar.bz2 and
>>binutils-blah-tar.bz2 in an ash+binutils directory.
>
>But subdirs are okay -- and already work.  E.g.:
>
>latest/ncurses/ncurses*.tar.bz2
>latest/ncurses/setup.hint (for the ncurses package)
>latest/ncurses/libncurses5/libncurses5*.tar.bz2
>latest/ncurses/libncurses5/setup.hint (for the libncurses5 package)
>latest/ncurses/libncurses6/libncurses6*.tar.bz2
>latest/ncurses/libncurses6/setup.hint (for the libncurses6 package)
>
>BUT, everything under latest/ncurses/ is directly related to ncurses itself.

One additional level of subdirs are ok.

cgf

--
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-17 17:55 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2001-11-11  8:26   ` Robert Collins
2001-11-11  8:26     ` Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2001-11-11  8:26 David A. Cobb
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       ` 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       ` Robert Collins
2001-11-11  8:26       ` Charles Wilson
2001-11-11  8:26         ` John Marshall
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               ` 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               ` Charles Wilson
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         ` Stipe Tolj
2001-11-11  8:26           ` Robert Collins
2001-11-11  8:26             ` Stipe Tolj
2001-11-11  8:26               ` Robert Collins

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=20011117175553.GA23825@redhat.com \
    --to=cgf@redhat.com \
    --cc=cygwin@cygwin.com \
    /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).