From: "V.Krishn" <vkrishn4@gmail.com>
Reply-To: vkrishn4@gmail.com
To: alpine-devel@lists.alpinelinux.org
Subject: [alpine-devel] Packaging convention for 3rd party
Date: Wed, 20 Nov 2013 19:41:31 +0530
User-Agent: KMail/1.13.7 (Linux/3.9.6-64; KDE/4.8.4; x86_64; ; )
Precedence: list
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <201311201941.31262.vkrishn4@gmail.com>


I was planning to package few web based files like js/css.
Releasing for or building with Alpine main repo would not be 
much benefit as they are suited for specific application.

Was wanting to know what would be the best method/practice 
to release such pkgs ?
Any convention/norms in file naming, so that it can be 
distinguished from other/main packagers ?

-- 
Regards.
V.Krishn


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---