Re: Removing w32 specific Python code from a package
On Thu, 2009-02-26 at 16:27 +0100, Adeodato Simó wrote: * Stephan Peijnik [Thu, 26 Feb 2009 15:46:58 +0100]: Now as python-pyglet needs to be repacked because it is not entirely free anyways I thought I could get rid of this problem by simply removing the w32-specifics when repackaging the dfsg version of the tarball. What about just not installing into the .deb the windows-specific files? I file a bug-report upstream and asked them to fix that in their setup.py. Maybe I could remove that code in the build target of debian/rules. Is that what you suggested? -- Stephan signature.asc Description: This is a digitally signed message part
Re: Removing w32 specific Python code from a package
* Stephan Peijnik [Fri, 27 Feb 2009 10:07:40 +0100]: On Thu, 2009-02-26 at 16:27 +0100, Adeodato Simó wrote: * Stephan Peijnik [Thu, 26 Feb 2009 15:46:58 +0100]: Now as python-pyglet needs to be repacked because it is not entirely free anyways I thought I could get rid of this problem by simply removing the w32-specifics when repackaging the dfsg version of the tarball. What about just not installing into the .deb the windows-specific files? I file a bug-report upstream and asked them to fix that in their setup.py. Maybe I could remove that code in the build target of debian/rules. Is that what you suggested? More in the binary, but something like that, yes: setup.py install rm -f debian/python-pyglet/usr/share/.../bad.py ... -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org The first step on the road to wisdom is the admission of ignorance. The second step is realizing that you don't have to blab it to the world. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Leaving DPMT?
On Thu, Feb 26, 2009 at 22:11, Ondrej Certik ond...@certik.cz wrote: Currently I think Sandro is the last major contributor for DPMT who wants to stay in svn. No, what I said was: - I see no need to move to git as a team - I can't afford to download all the git repos for packages I want to modify once - My position must not stop the team to migrate to something else, if decided, but my contributions will be re-evaluated if it will happen Now, don't restart that discussion if nothing has changed. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Leaving DPMT?
First of all, I do not consider myself to be a 'major' contributor to the DPMT either. On Fri, 2009-02-27 at 15:07 +0100, Sandro Tosi wrote: No, what I said was: - I see no need to move to git as a team - I can't afford to download all the git repos for packages I want to modify once I can to some agree with Sandro here. I'm not a big fan of svn, but for the DPMT repository svn looks like the right choice to me. The big benefit of using svn is that each and every directory in a svn repository can be checked out forming a stand-alone local copy. And this exactly is not possible with other recently more-popular VCS such as Mercurial and git. Well, it would be possible to create a separate repository for each and every package, but as Piotr already put it, it would make certain tasks harder to achieve. Just think of the X-Svn-* to Svn-* field change recently. With separate repositories for each package one would first have to look up every repository URL, check out all of them, then apply the change to all of them and push all of them back. With svn it is as simple as checking out one directory (ie. packages/), apply the change and then do a single commit, which will push back all changes. Now the svn way seems a lot less complex to me, and that's why I would prefer staying with svn. However, if someone can point out that a 'better' vcs that has this 'every-directory-can-be-a-repository' behaviour, please do so and I would be happy to give that a try. Oh, last but not least, there's the old saying 'never change a running system', which one should really keep in mind when discussing such changes. -- Stephan signature.asc Description: This is a digitally signed message part
Re: Leaving DPMT?
On Fri, Feb 27, 2009 at 7:33 AM, Stephan Peijnik deb...@sp.or.at wrote: First of all, I do not consider myself to be a 'major' contributor to the DPMT either. On Fri, 2009-02-27 at 15:07 +0100, Sandro Tosi wrote: No, what I said was: - I see no need to move to git as a team - I can't afford to download all the git repos for packages I want to modify once I can to some agree with Sandro here. I'm not a big fan of svn, but for the DPMT repository svn looks like the right choice to me. The big benefit of using svn is that each and every directory in a svn repository can be checked out forming a stand-alone local copy. And this exactly is not possible with other recently more-popular VCS such as Mercurial and git. Well, it would be possible to create a separate repository for each and every package, but as Piotr already put it, it would make certain tasks harder to achieve. Just think of the X-Svn-* to Svn-* field change recently. With separate repositories for each package one would first have to look up every repository URL, check out all of them, then apply the change to all of them and push all of them back. With svn it is as simple as checking out one directory (ie. packages/), apply the change and then do a single commit, which will push back all changes. Now the svn way seems a lot less complex to me, and that's why I would prefer staying with svn. However, if someone can point out that a 'better' vcs that has this 'every-directory-can-be-a-repository' behaviour, please do so and I would be happy to give that a try. Oh, last but not least, there's the old saying 'never change a running system', which one should really keep in mind when discussing such changes. We discussed that in the pust, just find the discussion on this list before. I apologize for opening it again. Ondrej -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Leaving DPMT?
I see this discussion focussing exclusively on Subversion versus Git; I wish with this message to point out that not all DVCSen are necessarily like Git. To do so, I'll engage in a little advocacy for Bazaar. I hope people can be open to discussion about relative merits of tools. Stephan Peijnik deb...@sp.or.at writes: On Fri, 2009-02-27 at 15:07 +0100, Sandro Tosi wrote: No, what I said was: - I see no need to move to git as a team - I can't afford to download all the git repos for packages I want to modify once This issue is avoidable if the repository is a Bazaar one: Bazaar allows a centralised workflow with its “checkout” feature URL:http://bazaar-vcs.org/CheckoutTutorial URL:http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#using-checkouts. By default, a checkout causes any commits to the branch to *also* be committed to a remote branch. Optionally, a checkout can be “lightweight” which affords a workflow almost identical to that of Subversion: no initial download of the revision data, all commits are made to the remote repository only URL:http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#getting-a-lightweight-checkout. Of course, any Bazaar branch (whether a checkout or not) still allows all the DVCS behaviour, getting revision data from the repository as needed. I can to some agree with Sandro here. I'm not a big fan of svn, but for the DPMT repository svn looks like the right choice to me. The big benefit of using svn is that each and every directory in a svn repository can be checked out forming a stand-alone local copy. And this exactly is not possible with other recently more-popular VCS such as Mercurial and git. Bazaar, on the other hand, has a feature for this in newer versions (Bazaar 1.9 and later): you can create a “stacked branch”, allowing a casual contributor to get just that part of the repository URL:http://bazaar-vcs.org/Scenarios/OneOffContribution URL:http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#using-stacked-branches. With svn it is as simple as checking out one directory (ie. packages/), apply the change and then do a single commit, which will push back all changes. Just like this, except in a DVCS. However, if someone can point out that a 'better' vcs that has this 'every-directory-can-be-a-repository' behaviour, please do so and I would be happy to give that a try. For the “stacked branch” feature, you'll need Bazaar (package name ‘bzr’) version 1.9 or later. Debian ‘unstable' currently only has version 1.5; ‘experimental’ has version 1.12. For “checkout”, including the ‘--lightweight’ option, any version of Bazaar in Debian has this feature. Oh, last but not least, there's the old saying 'never change a running system', which one should really keep in mind when discussing such changes. Definitely. This advocacy is not at all intended as demand for change. -- \ “Don't be afraid of missing opportunities. Behind every failure | `\ is an opportunity somebody wishes they had missed.” —Jane | _o__) Wagner, via Lily Tomlin | Ben Finney -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Leaving DPMT?
On Sat, Feb 28, 2009 at 01:11, Ben Finney ben+deb...@benfinney.id.au wrote: I see this discussion focussing exclusively on Subversion versus Git; I wish with this message to point out that not all DVCSen are necessarily like Git. WTF?! As Ondrej said just some hours ago: On Fri, Feb 27, 2009 at 16:41, Ondrej Certik ond...@certik.cz wrote: We discussed that in the pust, just find the discussion on this list before. I apologize for opening it again. Use the right thread to discuss this. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Leaving DPMT?
Sandro Tosi mo...@debian.org writes: On Sat, Feb 28, 2009 at 01:11, Ben Finney ben+deb...@benfinney.id.au wrote: I see this discussion focussing exclusively on Subversion versus Git; I wish with this message to point out that not all DVCSen are necessarily like Git. WTF?! As Ondrej said just some hours ago: I didn't see that message when I wrote mine. On Fri, Feb 27, 2009 at 16:41, Ondrej Certik ond...@certik.cz wrote: We discussed that in the pust, just find the discussion on this list before. I apologize for opening it again. I don't know what thread that is. Use the right thread to discuss this. Certainly, if someone can point me to the right thread. -- \“I used to work in a fire hydrant factory. You couldn't park | `\ anywhere near the place.” —Steven Wright | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Leaving DPMT?
On Fri, Feb 27, 2009 at 4:48 PM, Ben Finney ben+deb...@benfinney.id.au wrote: Sandro Tosi mo...@debian.org writes: On Sat, Feb 28, 2009 at 01:11, Ben Finney ben+deb...@benfinney.id.au wrote: I see this discussion focussing exclusively on Subversion versus Git; I wish with this message to point out that not all DVCSen are necessarily like Git. WTF?! As Ondrej said just some hours ago: You seem quite fed-up Sandro. :) I didn't mean it to start the svn-git discussion again when I mentioned you. Just to check if you already fixed your internet connection or not yet. :) I didn't see that message when I wrote mine. On Fri, Feb 27, 2009 at 16:41, Ondrej Certik ond...@certik.cz wrote: We discussed that in the pust, just find the discussion on this list before. I apologize for opening it again. I don't know what thread that is. Use the right thread to discuss this. Certainly, if someone can point me to the right thread. http://www.google.com/search?hl=enq=debian+python+git+svnbtnG=Google+Searchaq=foq= it's the 4th link: http://www.mail-archive.com/debian-python@lists.debian.org/msg04997.html Ondrej -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Leaving DPMT?
Ondrej Certik ond...@certik.cz writes: On Fri, Feb 27, 2009 at 4:48 PM, Ben Finney ben+deb...@benfinney.id.au wrote: Certainly, if someone can point me to the right thread. http://www.google.com/search?hl=enq=debian+python+git+svnbtnG=Google+Searchaq=foq= it's the 4th link: http://www.mail-archive.com/debian-python@lists.debian.org/msg04997.html For future reference here's the official link to that message in Debian's own archive: URL:http://lists.debian.org/debian-python/2008/12/msg00083.html which allows easier followup (not least because it shows the Message-Id field). -- \ “Yesterday I saw a subliminal advertising executive for just a | `\ second.” —Steven Wright | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Developer workflow and DVCS (was: Leaving DPMT?)
[re-sending as a followup to an older thread] I see this discussion focussing on Subversion versus Git; I wish with this message to point out that's a false dichotomy, as not all DVCSen are necessarily like Git. To do so, I'll engage in a little advocacy for Bazaar URL:http://bazaar-vcs.org/. I hope people can be open to discussion about relative merits of tools. Stephan Peijnik deb...@sp.or.at writes: On Fri, 2009-02-27 at 15:07 +0100, Sandro Tosi wrote: No, what I said was: - I see no need to move to git as a team - I can't afford to download all the git repos for packages I want to modify once This issue is avoidable if the repository is a Bazaar one: Bazaar allows a centralised workflow with its “checkout” feature URL:http://bazaar-vcs.org/CheckoutTutorial URL:http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#using-checkouts. By default, a checkout causes any commits to the branch to *also* be committed to a remote branch. Optionally, a checkout can be “lightweight” which affords a workflow almost identical to that of Subversion: no initial download of the revision data, all commits are made to the remote repository only URL:http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#getting-a-lightweight-checkout. Of course, any Bazaar branch (whether a checkout or not) still allows all the DVCS behaviour, getting revision data from the repository as needed. I can to some agree with Sandro here. I'm not a big fan of svn, but for the DPMT repository svn looks like the right choice to me. The big benefit of using svn is that each and every directory in a svn repository can be checked out forming a stand-alone local copy. And this exactly is not possible with other recently more-popular VCS such as Mercurial and git. Bazaar, on the other hand, has a feature for this in newer versions (Bazaar 1.9 and later): you can create a “stacked branch”, allowing a casual contributor to get just that part of the repository URL:http://bazaar-vcs.org/Scenarios/OneOffContribution URL:http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#using-stacked-branches. With svn it is as simple as checking out one directory (ie. packages/), apply the change and then do a single commit, which will push back all changes. Just like this, except in a DVCS. However, if someone can point out that a 'better' vcs that has this 'every-directory-can-be-a-repository' behaviour, please do so and I would be happy to give that a try. For the “stacked branch” feature, you'll need Bazaar (package name ‘bzr’) version 1.9 or later. Debian ‘unstable' currently only has version 1.5; ‘experimental’ has version 1.12. For “checkout”, including the ‘--lightweight’ option, any version of Bazaar in Debian has this feature. Oh, last but not least, there's the old saying 'never change a running system', which one should really keep in mind when discussing such changes. Definitely. This advocacy is not at all intended as demand for change. -- \ “Don't be afraid of missing opportunities. Behind every failure | `\ is an opportunity somebody wishes they had missed.” —Jane | _o__) Wagner, via Lily Tomlin | Ben Finney -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
