[Daniel15]

That'd probably be in the Makefile (or the configure script), not in the .bashrc. It'd differ per app depending on what make system the app uses.

[_Sam]

Well there are 3 different repositories and I can't check that change in so it would be local and lost on the next update or checkout. So I'd prefer a solution that is only local and does not touch the code.
The version number is in a file and I prefer to set that version number before the make, but I tend to forget it so I want to be forced to put it in.

[Quinn]

Well, you could do an alias.

alias make='{ADD VERSION NUMBER TO TEXT FILE} && make'

Edit: Don't take my word for it though, I'm not 100% sure that this would work.

[Ruku]

In your

.bashrc

:

make () {
    if [ "$1" != "clean" ]; then
        "$EDITOR" yourfile.txt
    fi

    "$(which make)" $@
}

[lobabob]

I think .bashrc gets overwritten with updates. I would put:

make () {
    if [ "$1" != "clean" ]; then
        "$EDITOR" yourfile.txt
    fi

    "$(which make)" $@
}
alias make=make

in .bash_aliases instead of .bashrc

[Cyril]

.bash_profile anyone?

[Ruku]

lobabob, on 08 July 2012 - 01:27 AM, said:

I think .bashrc gets overwritten with updates. I would put:

make () {
    if [ "$1" != "clean" ]; then
        "$EDITOR" yourfile.txt
    fi

    "$(which make)" $@
}
alias make=make

in .bash_aliases instead of .bashrc

No it doesn't!

/etc/bashrc

will be, but on any decent operating system the files in your hone directory are your own and won't be overwritten on a whim. The files in your hone directory generally source the global ones in

/etc

, then the user may specify their preferences afterwards, thus taking priority. I've never seen the users files modified, so I'd be sending a ranty email to your system administrator

@Cyril

.bash_profile

is generally used to set up agent applications and such. I'd recommend using the RC (run time configuration file.

[Quinn]

Ruku, on 08 July 2012 - 02:01 PM, said:

No it doesn't!

/etc/bashrc

will be, but on any decent operating system the files in your hone directory are your own and won't be overwritten on a whim. The files in your hone directory generally source the global ones in

/etc

, then the user may specify their preferences afterwards, thus taking priority. I've never seen the users files modified, so I'd be sending a ranty email to your system administrator

I thought the first one was a simple typo, but two of them? I thought better of you D:

[callumacrae]

Quinn, on 08 July 2012 - 02:25 PM, said:

I thought the first one was a simple typo, but two of them? I thought better of you D:

They renamed it a couple years back, home is a silly name >_<

[Ruku]

Quinn, on 08 July 2012 - 02:25 PM, said:

I thought the first one was a simple typo, but two of them? I thought better of you D:

Auto complete in ICS sucks. I corrected it manually once but it seems to have corrected it back again!?

[_Sam]

Thanks Ruku your answer helped me a lot.
This is what I finally came up with:

make () {
        if [ -f $1 ] ; then
                if [ $BUILD_ROOT ] ; then
                        if [[ $PWD = */int ]] ; then
                                vi $BUILD_ROOT/../releases/release.nbr
                        fi
                fi
        fi
        "$(which make)" $@
}

I now only do it when there is no argument and when it's called from a certain folder.