On Sat, 19 May 2001, Mike Noyes wrote:
George,
We now have two methods for the cvs package directory.
A) tarball plus diff with a makefile
B) import original source and modify using cvs to create diffs
Should we allow developers to use the method they prefer for packages they
On Sat, 19 May 2001, Mike Noyes wrote:
Mike Noyes, 2001-05-19 07:14 -0700
We agree the package tree needs categories. Now the hard part, what should
they be? I think we need a scripts category. I have my doubts about
using a net category, because most of our packages fit into it.
Everyone,
Mike Noyes wrote:
Mike Noyes, 2001-05-19 07:14 -0700
We agree the package tree needs categories. Now the hard part, what should
they be? I think we need a scripts category. I have my doubts about
using a net category, because most of our packages fit into it.
Everyone,
What about the
George Metz, 2001-05-17 18:27 -0400
On Thu, 17 May 2001, Mike Noyes wrote:
Ewald,
Would this make it more difficult for us to track our changes to the
original tarballs?
That's fairly trivial to solve though; just do a cleanroom tree that
contains the original, as-released, unmodified
Ewald Wasscher, 2001-05-18 19:40 +0200
David Douthitt wrote:
George Metz wrote:
On Thu, 17 May 2001, Mike Noyes wrote:
We have over 100 packages that I'm aware of. I'm sure that number
will increase once we start importing packages into cvs. I think the
packages tree might get cluttered
Mike Noyes, 2001-05-19 07:14 -0700
We agree the package tree needs categories. Now the hard part, what should
they be? I think we need a scripts category. I have my doubts about
using a net category, because most of our packages fit into it.
Everyone,
What about the following four categories?
George Metz wrote:
On Thu, 17 May 2001, Mike Noyes wrote:
We have over 100 packages that I'm aware of. I'm sure that number will
increase once we start importing packages into cvs. I think the packages
tree might get cluttered without categories.
Agreed. Go take a stroll through the
David Douthitt wrote:
George Metz wrote:
On Thu, 17 May 2001, Mike Noyes wrote:
We have over 100 packages that I'm aware of. I'm sure that number will
increase once we start importing packages into cvs. I think the packages
tree might get cluttered without categories.
Agreed. Go take a stroll
Ewald Wasscher, 2001-05-17 22:33 +0200
Everybody,
I forget to mention that with *BSD you can check out the source code from
CVS and simply do something like:
root@mybsd:/usr/src # make world
And rebuild the entire system from scratch. I think that is so _very_
cool. That is one more reason
On Thu, 17 May 2001, Mike Noyes wrote:
Ewald,
Would this make it more difficult for us to track our changes to the
original tarballs?
That's fairly trivial to solve though; just do a cleanroom tree that
contains the original, as-released, unmodified source. Then you can diff
the cleanroom
Mike Noyes wrote:
Everyone,
I'm going to create the following directories in CVS on Thursday,
unless there are objections.
/release +
+ /eigerstein
+ /ladybug
+ /oxygen
+ /quercus
/script +
+ /weblet
+ (etc.)
/package +
Ewald Wasscher, 2001-05-16 19:13 +0200
Mike Noyes wrote:
Everyone,
I'm going to create the following directories in CVS on Thursday, unless
there are objections.
It's a little late perhaps, but I wonder about the usefulness of using cvs
for storing tarballs and diff files. That would mean e.g
Mike Noyes wrote:
Everyone,
I created the following trees in our CVS repository today. There are
README files in each tree describing the proposed content.
doc
package
release
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/
I didn't do anything else, because the discussion on
On Sun, 6 May 2001, Ewald Wasscher wrote:
Reaching such a consensus is imho on of the most important (if not the
most) things right now. So whatever agreements we make, we should make
them.
Agreed.
And preferably the discussion shouldn't be a 3 man discussion as
it has been until now.
George Metz, 2001-05-06 10:34 -0400
On Sun, 6 May 2001, Ewald Wasscher wrote:
Reaching such a consensus is imho on of the most important (if not the
most) things right now. So whatever agreements we make, we should make
them.
Agreed.
And preferably the discussion shouldn't be a 3 man
On 3 May 2001, at 10:44, Ewald Wasscher wrote:
[EMAIL PROTECTED] wrote:
I wound up using whatever diffs [for ash that]
Erik [Andersen] had.
Fair enough. If you could send me the diff that converts the makefile to
gnu-make style I'd be thankful.
Everything should be in the Oxygen ISO;
Mike Noyes wrote:
Ewald Wasscher, 2001-05-01 20:24 +0200
Mike Noyes wrote:
David proposed something like this already. Take a look at this patch.
Source code + diffs for CVS
https://sourceforge.net/tracker/?func=detailaid=412704group_id=13751
\
atid=313751
I like the basic idea
On Wed, 2 May 2001, Ewald Wasscher wrote:
[EMAIL PROTECTED] wrote:
[...]
What I had in mind was to do the same thing, but with patched sources
- and thus then create a package at the same time.
I would like to keep the lrp-specific things as seperate as possible
from the original
Ewald Wasscher, 2001-05-01 16:11 +0200
Mike Noyes wrote:
The package tree will mimic the Debian source tree. Diff files should
not be gziped. Other than that minor change, do what Debian does.
http://ftp.us.debian.org/debian/dists/stable/main/source/
Wouldn't it be a good idea to have a
On 1 May 2001, at 15:19, Ewald Wasscher wrote:
Wouldn't it be a good idea to have a default way of building packages,
like Debian? With Debian you can cd into the upacked/patched source
directory and do a dpkg-buildpackage -b and voila! a binary package
appears after a while. So we could
Everyone,
I'm going to create the following directories in CVS on Thursday, unless
there are objections.
/release +
+ /eigerstein
+ /ladybug
+ /oxygen
+ /quercus
/script +
+ /weblet
+ (etc.)
/package +
+ /base
+
KP Kirchdörfer, 2001-04-30 19:38 +0200
Am Montag, 30. April 2001 17:19 schrieben Sie:
Everyone,
I'm going to create the following directories in CVS on Thursday,
unless there are objections.
/release +
+ /eigerstein
+ /ladybug
+ /oxygen
+
22 matches
Mail list logo
