On Fri 22 Jan 2010 04:00:15 pm Michał Zając wrote:
> Dnia piÄ…tek 22 stycznia 2010 o 21:55:51 Roman Shtylman
napisał(a):
> > Are we tracking the kde sources in bazaar? With the big push
for
> > distributed development (or whatever it is called now), I was
> > wondering if the kde source tree for lucid is somewhere in
launchpad?
> > I did some initial digging but couldn't really locate it...
> >
> > Any pointers in the right direction? Thanks.
> >
> > ~Roman
>
> I belive we only track our debian/ dirs in bazaar but I can be
mistaken.
> The branches are owned by kubuntu-members IIRC.

Basically, yes. Technically Launchpad does have a branch of the
full KDE sources in bazaar, but we do not use them and they are
only updated when new packages are dput'd to Ubuntu.

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

hmm... I see... I thought they were moving to have the full source
tree in launchpad and use that for the building?

I have some changes/tweaks to my kdebase/libs which I wanna keep in
ppa or something and am just looking for the right approach to doing
that so that tracking my changes isn't a pain... currently I use
git to manage my stuff.

~Roman

On Fri, Jan 22, 2010 at 7:31 PM, Jonathan Thomas <echidnaman@gmail.com> wrote:
> On Fri 22 Jan 2010 04:00:15 pm Michał Zając wrote:
>> Dnia piÄ…tek 22 stycznia 2010 o 21:55:51 Roman Shtylman
> napisał(a):
>> > Are we tracking the kde sources in bazaar? With the big push
> for
>> > distributed development (or whatever it is called now), I was
>> > wondering if the kde source tree for lucid is somewhere in
> launchpad?
>> > I did some initial digging but couldn't really locate it...
>> >
>> > Any pointers in the right direction? Thanks.
>> >
>> > ~Roman
>>
>> I belive we only track our debian/ dirs in bazaar but I can be
> mistaken.
>> The branches are owned by kubuntu-members IIRC.
>
> Basically, yes. Technically Launchpad does have a branch of the
> full KDE sources in bazaar, but we do not use them and they are
> only updated when new packages are dput'd to Ubuntu.
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Am Samstag, 23. Januar 2010 05:16:47 schrieb Roman Shtylman:
> hmm... I see... I thought they were moving to have the full source
> tree in launchpad and use that for the building?
>
> I have some changes/tweaks to my kdebase/libs which I wanna keep in
> ppa or something and am just looking for the right approach to doing
> that so that tracking my changes isn't a pain... currently I use
> git to manage my stuff.

Well, unless you want to track against KDE trunk, you'd go like this:
create proper quilt patches of the changes and track those in a branch of the
regular packaging branch.
Quilt, being a super superior patch solution, doesn't add a lot of overhead
for updates.
Using tools such as bzr-buildpackage you can then create proper debian source
packages from that.

There are several implications that make full-source branches a super PITA for
KDE. Most importantly, since KDE consits of large meta source packages, the
revision history of one branch grows extremely fast, which would quite soon
make it impossible to work on those branches without super fast intarwebs
access (the larger the history the longer the initial branching takes...). So
we decided to not use full-source branches until there is a way to ensure that
even those with very slow internet access can still work on the branches.

hth
--
Harald Sitter
Kubuntu Core Developer
http://www.kubuntu.org
--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel