|Official Postfix source code repository?||Dāvis Mosāns||4/18/14 8:47 AM|
I couldn't find Postfix source code repository, I saw only tarballs.Is there any particular reason why there's no source code repository?
Source control (SCM/VCS) is a MUST have. It's unbelievable that people just work with tarballs without proper source control. It doesn't matter which you use, but it must be available. Sending patches over email is what people did last century...
I would suggest using Git, but any other would be fine too like Mercurial, Bazaar or even Subversion. Also I would suggest using GitHub for code hosting, but Bitbucket or Gitorious would also be fine, or you might host it yourself on your own server (such as GitLab).
|Re: Official Postfix source code repository?||li...@rhsoft.net||4/18/14 9:08 AM|
disclaimer: i am not the author of postfix, only *my* opinion
it is unbelieve that people coming new here and pissing around
in context of the best maintained and documented software
you are hardly in the position to say what muste be
i would suggest that you ask questions first or be quiet
the postfix author *is* using a VCS but he do not need
to provide access to you or me
there is one and if you would inform you before shout how postfix
is maintained and documented you would ask for access instead
coming in like an elephant and get access or a explaination
why the author prefers to keep it closed and only release tarballs
|Re: Official Postfix source code repository?||Jim Reid||4/18/14 9:37 AM|
On 18 Apr 2014, at 16:47, Dāvis Mosāns <davi...@gmail.com> wrote:> Source control (SCM/VCS) is a MUST have. It's unbelievable that people just
> work with tarballs without proper source control.It's unbelievable that kids these days see every software development/maintenance task as something that must get crushed under a git-shaped sledgehammer regardless of whether that's the reasonable or sensible thing to do. [Resistance is futile. Your code will be assimilated.] Has it not dawned on you that the reason something like git is not provided might be that it is simply the wrong tool for the job?
You are of course free to take the tarballs and feed them into the version control repository of your choice. That does not mean everyone else who works on postfix is obliged to work with whatever is your flavour of the month VCS. BTW, what contributions have you actually made to postfix?
> It doesn't matter which you use, but it must be available.
Why? The author of postfix gets to choose/control how others commit code. Put simply, it's Wietse's ball and he decides who can play with it and what they are allowed to do with it. You don't. One of the reasons why postfix has remained in good shape for ~20 years is because well-intentioned but clueless people don't get to throw in features or or chase passing fads or ride their personal hobby-horses. The most successful (and vital) open source projects operate in this way too. That's not a coincidence.
It will be a very sad day when someone is obliged to use git or subversion or... to get access to open source software. For 99%+ of the users, 99%+ of the time, all that's needed is to download a tarball -- kids, ask your dad about FTP -- unpack it and run make. Anything else is unnecessary overkill. That lesson appears to be lost on the next generation.
So what? It ain't broke and therefore doesn't need fixing. Especially by bloatware like git. Tools like that have their place -- projects with a cast of thousands perhaps (monkeys and typewriters spring to mind) -- but IMO postfix is not one of them.
|Re: Official Postfix source code repository?||Viktor Dukhovni||4/18/14 9:51 AM|
On Fri, Apr 18, 2014 at 05:37:26PM +0100, Jim Reid wrote:While the OP is trolling, and will be booted from the list if
trolling persists, please don't take the bait and launch into a
crusade against your favourite heresy.
Wietse does not use git, but he may some day. Whether he does or
does not use git, signed tarballs will for the forseeable future
continue to be the primary means by which Postfix releases are made
|OT: Official Postfix source code repository||Wietse Venema||4/18/14 9:51 AM|
> > I couldn't find Postfix source code repository, I saw only tarballs.Viktor keeps an unofficial GIT repository which is based on Postfix
releases and stuff that he works on himself. I expect that there
will be some public repository that is updated with each release,
but the public one would not be authoritative. And I would never
ever want to share any of my code before it is released.
|Re: Official Postfix source code repository?||Quanah Gibson-Mount||4/18/14 10:00 AM|
--On Friday, April 18, 2014 5:51 PM +0000 Viktor Dukhovni
I really detest the current trend of having no real releases and a lack of
tarballs from various source projects. While openldap has an entirely
public git repo, which is extremely useful for examinig discrete code
changes or gathering history, all official releases are and continue to be
done via tarballs. I.e., I think public source code repos can be extremely
useful tools, they are not a great way to push official releases of
Architect - Server
Zimbra :: the leader in open source messaging and collaboration
|Re: OT: Official Postfix source code repository||Quanah Gibson-Mount||4/18/14 10:02 AM|
--On Friday, April 18, 2014 1:51 PM -0400 Wietse Venema
<wie...@porcupine.org> wrote:As an aside, I would note that it is possible to do this with SCM systems.
I know Howard Chu maintains his own clone of the OpenLDAP source that he
works from, and then only pushes back into the public repo when he's
satisified with the results -- I.e., he only pushes what he feels is ready
to be available into the general code repo. It's also useful for testing
new strategies and features without affecting mainline.
|Re: OT: Official Postfix source code repository||Viktor Dukhovni||4/18/14 10:37 AM|
On Fri, Apr 18, 2014 at 12:51:42PM -0400, Wietse Venema wrote:Note, I do not promise a stable history for any of the development
branches. I squash commits at will, and delete branches once their
features are merged into an official release on the "master" branch
or the patch branch of an official release. (Thus the long-term
history includes only the official and snapshot releases, not
My repository is useful for comparing past Postfix releases, enabling
one to quickly determine which Postfix release first added or
removed some block of code. It is also substantially more compact
than a separate copy of each of the ~1000 tarballs representing
each of the commits.
|Re: Official Postfix source code repository?||Dāvis Mosāns||4/18/14 10:38 AM|
I've nothing against tarballs and I'm not saying that there shouldn't be tarballs. I'm also not saying that repository could work as release distribution which it's not and I never said so. All I'm saying is that there also should be a source code repository with full commit history so that each code change could be reviewed. Tarballs only provide current source code, but not changesets which are very important. It seems like you're very ignorant and don't know what is right tool for right job. Do you really expect for people diff over 100 tarball releases to find which version introduced some bug or changed something on which you relied? Why do you think I asked for repository? because I was intending to contribute. Linux kernel uses git repository and that works perfectly fine.
2014-04-18 19:37 GMT+03:00 Jim Reid <j...@rfc1035.com>:
|Re: Official Postfix source code repository?||Wietse Venema||4/18/14 10:54 AM|
I'm closing this thread: take it off list or be removed. Postfix
is not the Linux kernel, and any comparison between the two is not
|Re: OT: Official Postfix source code repository||Dāvis Mosāns||4/18/14 11:14 AM|
That is exactly what I was looking for, just public read-only repository for main/master branch. It looks like it's this https://github.com/vdukhovni/postfix ? Only downside is that there's no useful commit messages. So basically have to look at commit individually to see what exactly was changed. At least blame works fine and can see which version changed respective code line. Do you also accept PRs or only way is patches in email?
And it's great that public repository is planned. Thanks.