At 8:17 Uhr -0400 07.04.2002, David R. Morrison wrote:
> > what is foo.dev? i've never heard of a .dev file...just curious.
>
>It was a typo for foo.deb .
>
>You can run "fink validate" on a .deb file and it will warn you about things
>that have been placed in non-policy-compliant locations.
Jus
> what is foo.dev? i've never heard of a .dev file...just curious.
It was a typo for foo.deb .
You can run "fink validate" on a .deb file and it will warn you about things
that have been placed in non-policy-compliant locations.
-- Dave
___
Fink-de
David R. Morrison [[EMAIL PROTECTED]] wrote:
> Any new packages that you write, or updates to packages that you maintain,
> are fine to check in to the unstable directory. The important things
> to keep in mind about CVS are: (1) nothing goes to stable until it has
> been throughly tested by othe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, April 6, 2002, at 10:28 PM, David R. Morrison wrote:
...
> (3) check to make sure that the things you
> are committing comply with fink's various policies. "fink validate
> foo.info"
> and "fink validate foo.dev" are very handy tools
Any new packages that you write, or updates to packages that you maintain,
are fine to check in to the unstable directory. The important things
to keep in mind about CVS are: (1) nothing goes to stable until it has
been throughly tested by other users, (2) except for immediately-committed
bugfixe
Since I'm "the new guy" as far as CVS access, I wanted to get an OK before
I do anything; I've got a number of perl modules I've packaged up that I use
myself for various scripts. Is it OK if I add them to unstable, or does
someone want to look them over first?
convert-tnef-pm-0.17-1.info
mailto
