TIP: Click on subject to list as thread! ANSI
echo: fidosoft.husky
to: All
from: Benny Pedersen
date: 2014-08-10 16:08:50
subject: husku using local include

Hello All!

structure of husky includes is not imho well formed, it makes it hard to
make gentoo ebuilds with depends in order, so thats where i cant make it
right, if husky did use global includes it would have being much more
simple, i will have to rewrite my gentoo ebuilds to use local includes to
make it stable, even there its not stable since its fetched from cvs :(

can some debian/ubuntu maintainers tell me how thay handle this in build time ?

are devs consistent of stable tag or dev builds ?

can we drop husky 1.4 and begin 2.0 ?, where 1.4 and 1.9 goes to the
unstable tagged in cvs ?


 Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/3.14.14-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)
SEEN-BY: 3/0 633/267 280 640/384 712/0 550 848 770/1
@PATH: 230/0 150 261/38 712/848 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.