FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 06-10-2010, 09:44 PM
Jesse Keating
 
Default dist-git project update

It's been a while since I last updated folks on dist-git, and in reality
it's been a while since I last worked on it. Fedora 13 took up all my
time.

Since my last update we've made great progress on fedpkg, the new tool
that will replace the make system. It is packaged up with
fedora-packager and has the ability to do many tasks that our Make
system handled. Here is a quick list:

build
chainbuild
clean
clog
clone
compile
gimmespec
install
lint
local
mockbuild
new
new_sources
prep
scratchbuild
sources
srpm
unusedpatches
verrel

Many of these targets take optional arguments which extend their
functionality and replace some other specific Make targets. This list
is enough to get us checking code out and in, and building in koji.

On the koji front we've recently discovered the changes necessary to
build from dist-git style repos, and those changes are being polished up
and committed upstream. We have done multiple builds successfully from
dist-git repos.

Where do we go from here?

We're ready for more wide scale testing, and to facilitate that I am
refreshing the git repos from current CVS (people with existing clones
will have to blow them away and re-clone), and getting a koji stage
instance up that we can build against (with limited builders). We'll
then push out another fedora-packager update that has the right URLs to
build against this stage Koji and announce that it is ready for
building.

Based on this testing, and some decisions around git tagging and branch
usage, we stand a good chance at being able to roll this out prior to
the F14 branch event. I hope you are all as excited as I am about this!

--
Jesse Keating
Fedora -- Freedom˛ is a feature!
identi.ca: http://identi.ca/jkeating
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-11-2010, 01:41 AM
Jarod Wilson
 
Default dist-git project update

On Thu, Jun 10, 2010 at 5:44 PM, Jesse Keating <jkeating@redhat.com> wrote:
> It's been a while since I last updated folks on dist-git, and in reality
> it's been a while since I last worked on it. *Fedora 13 took up all my
> time.
>
> Since my last update we've made great progress on fedpkg, the new tool
> that will replace the make system. *It is packaged up with
> fedora-packager and has the ability to do many tasks that our Make
> system handled.
...
> Based on this testing, and some decisions around git tagging and branch
> usage, we stand a good chance at being able to roll this out prior to
> the F14 branch event. *I hope you are all as excited as I am about this!

Oh hell yeah. Looking forward to the day when none of the projects I
work on are using cvs any longer (this includes you, Red Hat internal
cvs, and you, lirc upstream)...

--
Jarod Wilson
jarod@wilsonet.com
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-11-2010, 07:46 PM
Ryan Rix
 
Default dist-git project update

On Thu 10 June 2010 2:44:47 pm Jesse Keating wrote:
> It's been a while since I last updated folks on dist-git, and in reality
> it's been a while since I last worked on it. Fedora 13 took up all my
> time.
>
> Since my last update we've made great progress on fedpkg, the new tool
> that will replace the make system. It is packaged up with
> fedora-packager and has the ability to do many tasks that our Make
> system handled. Here is a quick list:
>
> build
> chainbuild
> clean
> clog
> clone
> compile
> gimmespec
> install
> lint
> local
> mockbuild
> new
> new_sources
> prep
> scratchbuild
> sources
> srpm
> unusedpatches
> verrel
>
> Many of these targets take optional arguments which extend their
> functionality and replace some other specific Make targets. This list
> is enough to get us checking code out and in, and building in koji.
>
> On the koji front we've recently discovered the changes necessary to
> build from dist-git style repos, and those changes are being polished up
> and committed upstream. We have done multiple builds successfully from
> dist-git repos.
>
> Where do we go from here?
>
> We're ready for more wide scale testing, and to facilitate that I am
> refreshing the git repos from current CVS (people with existing clones
> will have to blow them away and re-clone), and getting a koji stage
> instance up that we can build against (with limited builders). We'll
> then push out another fedora-packager update that has the right URLs to
> build against this stage Koji and announce that it is ready for
> building.
>
> Based on this testing, and some decisions around git tagging and branch
> usage, we stand a good chance at being able to roll this out prior to
> the F14 branch event. I hope you are all as excited as I am about this!

How will this affect current packagers' workflow? Will the changes necessary
be documented on the wiki? It doesn't seem straight off the bat that this
would be a drop-in replacement without packagers needing to tweak their
workflow.

Ryan

--
Ryan Rix
== http://hackersramblings.wordpress.com | http://rix.si/ ==
== http://rix.si/page/contact/ if you need a word ==
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-11-2010, 09:09 PM
Jesse Keating
 
Default dist-git project update

On Fri, 2010-06-11 at 12:46 -0700, Ryan Rix wrote:
> How will this affect current packagers' workflow? Will the changes necessary
> be documented on the wiki? It doesn't seem straight off the bat that this
> would be a drop-in replacement without packagers needing to tweak their
> workflow.
>

Packager workflow will indeed be affected. First and foremost they will
need to make use of 'fedpkg'. Fedpkg is replacing the Make system, and
adding a few things on top of it. Today to check out a package and
build it for rawhide you'd essentially do:

cvs <junk here> checkout <module>

cd <module>/devel/

edit junk

cvs add/commit

make tag

make build

With dist-git it's slightly different:

fedpkg clone <module>

cd <module>

edit junk

fedpkg commit (this target is missing right now, alternatively "git
commit")

fedpkg build


We've kept the target names the same, so "make foo" largely becomes
"fedpkg foo". But since fedpkg can take options for the targets much
easier than make can, some targets grew options, like "fedpkg build
--scratch" which essentially does "fedpkg scratch-build". Also, where
with the Make system we'd have to pass arguments as env variables (make
new-sources FILES=blah..) we can do it as arguments: fedpkg new-sources
file1 <file2> <file3>.

We also are able to put in a better help system, so that fedpkg --help
and fedpkg <target> --help provide better help to end users trying to
get things done.

--
Jesse Keating
Fedora -- Freedom˛ is a feature!
identi.ca: http://identi.ca/jkeating
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-11-2010, 09:21 PM
Simo Sorce
 
Default dist-git project update

On Fri, 11 Jun 2010 14:09:41 -0700
Jesse Keating <jkeating@redhat.com> wrote:

> With dist-git it's slightly different:
>
> fedpkg clone <module>

Is it necessary to do fedpkg clone ?
Or can regular git be used ?

Simo.

--
Simo Sorce * Red Hat, Inc * New York
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-11-2010, 09:57 PM
Jesse Keating
 
Default dist-git project update

On Fri, 2010-06-11 at 17:21 -0400, Simo Sorce wrote:
>
> Is it necessary to do fedpkg clone ?
> Or can regular git be used ?
>
>
Not necessary at all. The current url is
pkgs.stg.fedoraproject.org/<package> and that works with git:// and
ssh://. One advantage to using fedpkg clone is that if you like the
current directory layout where each release is a subdir, you can do
'fedpkg clone --branches' and you'll get that layout. You can also do
fedpkg clone -b <branch> and get a checkout of the specific branch
listed. By no means is fedpkg required for the clones and commits, but
it is a convenience that some will like to use, and will likely be the
"documented" way of doing things.

--
Jesse Keating
Fedora -- Freedom˛ is a feature!
identi.ca: http://identi.ca/jkeating
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-12-2010, 06:22 AM
Iain Arnell
 
Default dist-git project update

On Fri, Jun 11, 2010 at 11:57 PM, Jesse Keating <jkeating@redhat.com> wrote:
> The current url is
> pkgs.stg.fedoraproject.org/<package> *and that works with git:// and
> ssh://.

Any chance of making that work with http:// and https:// (for pushes) too?


--
Iain.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-12-2010, 07:39 PM
Jochen Schmitt
 
Default dist-git project update

Am 11.06.2010 23:57, schrieb Jesse Keating:
> ssh://. One advantage to using fedpkg clone is that if you like the
> current directory layout where each release is a subdir, you can do
> 'fedpkg clone --branches' and you'll get that layout. You can also do
> fedpkg clone -b <branch> and get a checkout of the specific branch
>
It's seems, that this feature is not implemented in the current
fedora-packager package.

when I try to make a fedpkg cloone --branches I will get only
a message which describe the function for this command without
any visible result.

Best Regards:

Jochen Schmitt
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-13-2010, 04:26 PM
Christopher Brown
 
Default dist-git project update

Hi Jesse,

On 11 June 2010 22:57, Jesse Keating <jkeating@redhat.com> wrote:
> On Fri, 2010-06-11 at 17:21 -0400, Simo Sorce wrote:
>>
>> Is it necessary to do fedpkg clone ?
>> Or can regular git be used ?
>>
>>
> Not necessary at all. *The current url is
> pkgs.stg.fedoraproject.org/<package> *and that works with git:// and
> ssh://. *One advantage to using fedpkg clone is that if you like the
> current directory layout where each release is a subdir, you can do
> 'fedpkg clone --branches' and you'll get that layout. *You can also do
> fedpkg clone -b <branch> and get a checkout of the specific branch
> listed. *By no means is fedpkg required for the clones and commits, but
> it is a convenience that some will like to use, and will likely be the
> "documented" way of doing things.

I'm really keen to see this come off as I think pretty much everyone
is and look forward to the day when we all bid cvs goodbye. Would it
not be saner to extend git through a plugin to provide fedora-specific
stuff rather than use a new, separate command like fedpkg? Might help
the migration if people understand that they are essentially using git
with a few fedora options instead.

Just a thought.

Regards

--
Christopher Brown
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-13-2010, 04:54 PM
Kevin Kofler
 
Default dist-git project update

Jesse Keating wrote:
> I hope you are all as excited as I am about this!

Count me as not excited.

As I already pointed out several times, I don't see anything obviously wrong
with our CVS setup, so I don't see what we have to gain from switching to
one of the hardest to use SCM systems out there.

Kevin Kofler

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 

Thread Tools




All times are GMT. The time now is 04:11 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org