Re: Buildj + Quickly Vala template == Love :)

[Shane Fagan <shanepatrickfagan ubuntu com>]

So by global patterns you mean just looking for the file type or mime
type to ensure you are getting the right thing right? That would be ok
but personally id like to restrict it to specific folders to promote
good programming practice in terms of project structures but I suppose
for a build system keeping it as general as possible is a good idea.

--fagan

On Thu, 2010-09-30 at 23:54 +0100, Alberto Ruiz wrote:
> Hi Shane,
> I think that using ant global patterns is a better idea. I don't want
> *magic* or implicit stuff that can go unnoticed. Note that you may
> want different programs using different .vala files.
> 
> I have to add support for "**/*.vala" if you find listing all the
> files might be annoying.
> 
> 2010/9/30 Shane Fagan <shanepatrickfagan ubuntu com>:
> > Hey Alberto,
> >
> > Well for building you need to know where all of the .vala files are and
> > the images...etc so the idea im having is that you can scan dirs for to
> > see where all of that info is. So I have a set place for all of that
> > stuff to cut that out of the config files.
> >
> > Oh and I have news a guy over at Canonical was working today on the
> > depends detection and its kinda working now. The only issue is that
> > people are jumping on the wrong namespaces in their .vapi files so its
> > just a case of getting that fixed and we are golden there.
> >
> > --fagan
> >
> > On Thu, 2010-09-30 at 22:36 +0100, Alberto Ruiz wrote:
> >> Hi Shane,
> >> I am not sure I understand what you mean, can you elaborate a bit?
> >>
> >> 2010/9/30 Shane Fagan <shanepatrickfagan ubuntu com>:
> >> > Oh i forgot to ask if thats a good plan to have set dirs for specific
> >> > files so that buildj can just scan the dirs for the info. (if that makes
> >> > sense)
> >> >
> >> > --fagan
> >> >
> >> > On Tue, 2010-09-28 at 12:12 +0100, Alberto Ruiz wrote:
> >> >> Hello Shane,
> >> >> glad to know your interest in buildj, Quickly is exactly the kind of
> >> >> thing I had in mind when I came up with this.
> >> >>
> >> >> I have just fixed some remaining bugs in the vala support in waf/trunk
> >> >> so things should be fine on this camp.
> >> >>
> >> >> What we need help at right now:
> >> >>
> >> >> Moving from JSON to YAML, abderrahim is working on a small yaml parser
> >> >> that we can embed since the ones available are too big and we only
> >> >> need a subset of yaml.
> >> >>
> >> >> Abderrahim, any news on this side?
> >> >>
> >> >>
> >> >>
> >> >> 2010/9/23 Shane Fagan <shanepatrickfagan ubuntu com>:
> >> >> > Hey all,
> >> >> >
> >> >> > I hate build systems at the moment so I talked with Alberto over the
> >> >> > week and I was saying I want to use buildj for my Quickly Vala template.
> >> >> > So im going to share my ideal building situation for users.
> >> >> >
> >> >> > Oh and I should say what Quickly is first. Quickly is simply a system to
> >> >> > make development more automated. You have a template and a set of
> >> >> > commands to use. So quickly create <project name> creates the project,
> >> >> > quickly package, packages the project, quickly share pushes it to a ppa
> >> >> > on launchpad and so on. The idea is to keep config from the user to a
> >> >> > minimum so the user just has to focus on development.
> >> >> >
> >> >> > The main thing is that we have a fully automated process in place for
> >> >> > the user.
> >> >> >
> >> >> > So for that we need depends detection a la python-distutils-extra (ill
> >> >> > try to get this working on my end for ubuntu's 11.04 release)
> >> >> >
> >> >> > 1 config file that takes in the needed info for the packaging and
> >> >> > building.
> >> >> >  * author (+email too for packaging), app name, description, URL
> >> >> >  * version numbers in quickly are bumped automatically so that isnt
> >> >> > needed in the 1 file.
> >> >> >  * where the files are should be static bin files in /bin lib files
> >> >> > in /project_name and data like .ui files and images in /data (in
> >> >> > subfolders /ui and /media)
> >> >> >
> >> >> > So the idea is to keep it to a very simple config and make everything as
> >> >> > automated as possible. So the user says quickly package and buildj kicks
> >> >> > in and works out all of the hard building related stuff like where all
> >> >> > the pieces are and ill work out the debian directory stuff and the files
> >> >> > needed to create a package.
> >> >> >
> >> >> > So to make it easy for buildj to do its job ill be making a standard
> >> >> > layout of a quickly project for the users to stick to. So buildj will
> >> >> > just have to scan those directories and check for the files.
> >> >> >
> >> >> > gettext support should be automated too but id need someone who is an
> >> >> > expert to look at it.
> >> >> >
> >> >> > Ok so thats my ideas if it makes sense and we can do it awesome. Its all
> >> >> > up for discussion anyway and hopefully you guys can add to it.
> >> >> >
> >> >> > --fagan
> >> >> >
> >> >> > _______________________________________________
> >> >> > buildj-list mailing list
> >> >> > buildj-list gnome org
> >> >> > http://mail.gnome.org/mailman/listinfo/buildj-list
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >>
> >>
> >>
> >
> >
> >
> 
> 
>