1 files changed, 77 insertions, 0 deletions
diff --git a/archives/extend/2013-January/000040.html b/archives/extend/2013-January/000040.html
new file mode 100644
index 00000000..81f5ad61
--- /dev/null
+++ b/archives/extend/2013-January/000040.html
@@ -0,0 +1,77 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML>
+ <HEAD>
+   <TITLE> [99s-extend] Cowboy Makefile
+   </TITLE>
+   <LINK REL="Index" HREF="index.html" >
+   <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%20Makefile&In-Reply-To=%3C5101B89A.50604%40gjunka.com%3E">
+   <META NAME="robots" CONTENT="index,nofollow">
+   <style type="text/css">
+       pre {
+           white-space: pre-wrap;       /* css-2.1, curent FF, Opera, Safari */
+           }
+   </style>
+   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+   <LINK REL="Previous"  HREF="000042.html">
+   
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+   <H1>[99s-extend] Cowboy Makefile</H1>
+    <B>Grzegorz Junka</B> 
+    <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%20Makefile&In-Reply-To=%3C5101B89A.50604%40gjunka.com%3E"
+       TITLE="[99s-extend] Cowboy Makefile">list1 at gjunka.com
+       </A><BR>
+    <I>Thu Jan 24 23:41:30 CET 2013</I>
+    <P><UL>
+        <LI>Previous message: <A HREF="000042.html">[99s-extend] [erlang-questions] Cowboy feedback needed
+</A></li>
+        
+         <LI> <B>Messages sorted by:</B> 
+              <a href="date.html#40">[ date ]</a>
+              <a href="thread.html#40">[ thread ]</a>
+              <a href="subject.html#40">[ subject ]</a>
+              <a href="author.html#40">[ author ]</a>
+         </LI>
+       </UL>
+    <HR>  
+<!--beginarticle-->
+<PRE>Hi,
+I understand the move away from Rebar but I'd like to see the project to 
+be still Rebar-compatible. Would that be a problem? Mainly I am thinking 
+about dependencies. The Cowboy Makefile assumes that Ranch is in its 
+deps folder. If Cowboy is a part of a bigger application, and most often 
+it will be in such a role rather than a standalone application, then all 
+dependencies should be kept in one place. In that case it would be the 
+main project's deps folder, not Cowboy's deps folder. Can the 
+compilation process be split into compiling Cowboy dependencies 
+separately from Cowboy itself?
+
+something like:
+
+all: compile-deps compile-cowboy
+
+Then if Cowboy is a dependency itself it may be just compiled without 
+the dependency (as it will be compiled when the main project is compiled).
+
+
+</PRE>
+
+<!--endarticle-->
+    <HR>
+    <P><UL>
+        <!--threads-->
+	<LI>Previous message: <A HREF="000042.html">[99s-extend] [erlang-questions] Cowboy feedback needed
+</A></li>
+	
+         <LI> <B>Messages sorted by:</B> 
+              <a href="date.html#40">[ date ]</a>
+              <a href="thread.html#40">[ thread ]</a>
+              <a href="subject.html#40">[ subject ]</a>
+              <a href="author.html#40">[ author ]</a>
+         </LI>
+       </UL>
+
+<hr>
+<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend
+mailing list</a><br>
+</body></html>