git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Git List <git@vger.kernel.org>, Petr Baudis <pasky@ucw.cz>,
	Christian Couder <chriscool@tuxfamily.org>,
	Eric Wong <normalperson@yhbt.net>
Subject: Re: [PATCH GSoC] gitweb: Add global installation target for gitweb
Date: Sat, 15 May 2010 18:34:54 +0530	[thread overview]
Message-ID: <AANLkTilxlnUdfGEvpsaIKm3waSTGH_jUG9pW8ozc1PUJ@mail.gmail.com> (raw)
In-Reply-To: <201005151449.31609.jnareb@gmail.com>

>
> As I said, I agree with the reasoning and the fact that patch is split
> into two. What I disagree with is the splitting itself.
>
> Making 'install-gitweb' prerequisite to 'install' target, or in other
> words adding installing gitweb *somewhere*, should in my opinion by in
> this second patch.
>
>> I choose Makefile rather than choosing gitweb/Makefile becuase
>> git-instaweb is a package of git not a package of gitweb. So, I choose
>> Makefile rather than choosing gitweb/Makefile.
>
> This is important fact; the description that 'gitwebdir' has default
> value set (also) in Makefile because of the future change to the way
> git-instaweb is build / installed should be in commit message of a new
> first patch.
>
>
> BTW. if 'gitwebdir' would be set to some default value both in Makefile
> and in gitweb/Makefile, then in gitweb/Makefile the "?=" operator must
> be used (set if undefined).
>
> Note that default value in Makefile can be "$(sharedir)/gitweb", and in
> gitweb/Makefile can be '/var/www/cgi-bin'.
>
> [...]
>> > Two things.
>> >
>> > First, I think providing default value for 'gitwebdir' could be I good
>> > idea.  I think that all other build variables containing installation
>> > directories have default values.  But I do wonder whether the
>> > "$(sharedir)/gitweb" is a good default value for 'gitwebdir' (see also
>> > comment about git-instaweb below).
>>
>> I chose it because the lib files of gitk and git-gui are being
>> installed in sharedir.
>
> O.K., I can agree with this. You might want to put this substantiation
> in the commit message, though.
>
>> > Second, the issue with git-instaweb in its current form, and splitting
>> > gitweb is very important.  I am not sure though if this is correct
>> > solution for this problem.  It is NOT A FULL SOLUTION, that is sure.
>>
>> Yes, It is not a full solution. There is another patch that is
>> currently in discussion with my mentors.
>>
>> Petr and Christian told me to make sure that I send patches as small
>> as possibl so that they will be merged into the mainstream. That is my
>> GSoC aim too.
>>
>> So, I sent this small patch which just installs gitweb with git's
>> "make install" without breaking the git-instaweb.sh script.
>> The patch for modifying git-instaweb will be sent soon to his mailing list.
>
> That is a good practice, and a good idea.
>
> My complaints are about putting too much in this first patch (I think
> that making 'install' target install gitweb should be put in the commit
> that changes git-instaweb, as those two changes have to be
> synchronized), and about that commit message seems to claim that this
> commit does more than it really does.
>
> --
> Jakub Narebski
> Poland
>

So, what I need to do in this patch is add default values. Not
installing in 'install' target. ??
Or any thing else.

If you could specify what needs to be done, I will be happy resend the patch.

- Pavan

  reply	other threads:[~2010-05-15 13:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13  9:38 [PATCH GSoC] gitweb: Add global installation target for gitweb Pavan Kumar Sunkara
2010-05-14 15:07 ` Jakub Narebski
2010-05-14 16:40   ` Pavan Kumar Sunkara
2010-05-14 21:22     ` Jakub Narebski
2010-05-15 12:49     ` Jakub Narebski
2010-05-15 13:04       ` Pavan Kumar Sunkara [this message]
2010-05-15 18:43         ` Jakub Narebski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTilxlnUdfGEvpsaIKm3waSTGH_jUG9pW8ozc1PUJ@mail.gmail.com \
    --to=pavan.sss1991@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=normalperson@yhbt.net \
    --cc=pasky@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).