solaris/ and debian/ handling

Hi,

I thought about it a bit more, and came to this conclusion:
 - having distribution specific files in our repository
   is a good thing, if these files are maintained.
 - whether or not to include the files in the distribution
   tar file needs to be decided seperate for each case.
   For debian eric prefers not to have them in the tar file,
   for solaris it would be usefull, I think.
 - I don't see a big growth. debian, solaris, win32, rpm
   is all I can think of. *bsd people prefer to maintain
   those files in their own tree (ports collection), I think.

What I would like to do:
 - import debian/ from current debian releases (or to be exact:
   give eric write access so he can do that and update the files)
 - add solaris/ files from william (i.e. no packages/ subdir).
   Offer write access to william so he can update the files.
 - change Makefile* to include solaris/ files but not debian/ files.

Is this ok with everyone?

Thanks, Andreas


-- 
---------------------[ Ciphire Signature ]----------------------
From: aj@xxxxxxxxxxxxxxx signed email body (756 characters)
Date: on 22 March 2005 at 08:39:08 UTC
To:   opensc-devel@xxxxxxxxxx
----------------------------------------------------------------
: Ciphire has secured this email against identity theft.
: Free download at www.ciphire.com. The garbled lines
: below are the sender's verifiable digital signature.
----------------------------------------------------------------
00fAAAAAEAAACs2T9C9AIAAHkDAAIAAgACACBQ2JmUgw78JvBqhaOBPOsMFbVDS6
UaQIxcChG5IhzQhgEA0eMp7V0xI9MrMhC47uaTDnnuTnqi6z9oLEuev70rCXuXod
zypv52NnwN/kwdiv6KMlWPwujb1KiKUhhOrF6LzQ==
------------------[ End Ciphire Signed Message ]----------------