Re: [Fink-devel] new perl modules

2002-04-07 Thread David R. Morrison

 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-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] new perl modules

2002-04-07 Thread Max Horn

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.

Just to clarify one more thing: when fink check/fink validate 
complains, it usually means you have a problem that should be fixed. 
But if it does *not* complaint, then this doesn't have to mean your 
package is perfect! There are various problems that they don't catch 
currently, so don't relay on them alone, but also manually verify 
that you .deb files install into the correct place, and that they 
have actually all the files. Sometimes it's also a good idea to 
eyeball the output of the install phase of the package you are 
building, to verify it really installs into 
/sw/src/root-PACKAGE-VERSION-REV/ and not directly into /sw etc.


Max
-- 
---
Max Horn
Software Developer

email: mailto:[EMAIL PROTECTED]
phone: (+49) 6151-494890

___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] new perl modules

2002-04-06 Thread David R. Morrison

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
bugfixes, if you make a change which will affect the .deb file, you must
increase the revision number, (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 for this.

  -- Dave

___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] new perl modules

2002-04-06 Thread Chris Zubrzycki

-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 for this.

what is foo.dev? i've never heard of a .dev file...just curious.

- -chris zubrzycki
- - --
PGP public key: http://homepage.mac.com/beren/publickey.txt
ID: 0xA2ABC070
Fingerprint: 26B0 BA6B A409 FA83 42B3  1688 FBF9 8232 A2AB C070
_
This message is encoded using the Rot-26 encoding method.  Unauthorized 
decoding of this message may result in extreme penalties under the 
DMCA.  These penalties include, but are not limited to: US$100,000 fine, 
life imprisonment, castration, death, limp hair, terminal halitosis, and 
amputation of the extremities.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (Darwin)
Comment: For info see http://www.gnupg.org

iD8DBQE8r7/R+/mCMqKrwHARAnlEAJoDOO7poaJ23/dEYC3HYSiuhWawzQCfXA5Z
hI24ZTZLbnpLeiFZid4M0dk=
=5Uc9
-END PGP SIGNATURE-


___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel



Re: [Fink-devel] new perl modules

2002-04-06 Thread Benjamin Reed

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 other users, (2) except for immediately-committed
 bugfixes, if you make a change which will affect the .deb file, you must
 increase the revision number, (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 for this.

Yeah, they all pass validate, I'm just being paranoid.  =)

I'll bump the version on xml-dom-pm too, the only thing that changes
build-wise is the version number.  I'm sure Justin won't mind.

-- 
Benjamin Reed a.k.a. Ranger Rick ([EMAIL PROTECTED]) http://ranger.befunk.com/

___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel