Hi Craig,
Craig Austin wrote:
<snip>
>
> I think I merged too many thoughts here. Sorry. What I was really looking
> for was some documentation that said something to the effect of:
>
> "To make changes to <x> component, you will need to modify files <A>,
> <B>,
> and <C>...."
>
> Or
>
> "After making changes to a template file, you will need to run <such and
> such> script before the changes will be seen......"
>
> Or
>
> "If you make modifications to this component, you need to make sure you keep
> in mind these dependencies...."
If you let us know what specific areas you want to change we can do
something like this, but I don't think we have time / need too do this
for every component in the system. Let us know the things you want to
change and we can point out what you need to do. We will then document
this on the wiki for future reference.
>
>>I'm not familiar to how bugzilla does this. Could you elaborate on this,
>>please?
>>
>>--Joao
>
>
> I've only tinkered with bugZilla (until I found eventum...which is much
> better in my opinion), so I'm not speaking from a lot of experience. Their
> approach is pretty simple. There is folder named 'custom' that is initially
> empty. When you want to customize a file, you copy that file into the
> custom folder, then edit away. You keep the filename the same. The
> application first looks in the custom folder for a particular file, then if
> it's not found there, it looks in the regular path. I believe this only
> works when changing template files. It seemed to make it easier when
> getting updates to the core product.
>
> Of course, you could just keep track of which files you modified by
> yourself, so maybe it's not worth spending time doing something like this.
I believe this is what most people are doing at the moment. Especially
if you are only changing templates it should be fairly easy.
Best Regards,
/bryan
